ChainPyPI:Django
Django: successive fixes (2012–2014)
3 CVEs over 3 generations, 31 Jul 2012 to 16 May 2014.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2012-344231 Jul 2012 First in the chain
- CVE-2012-452018 Nov 2012 related to CVE-2012-3442
- CVE-2014-141816 May 2014 related to CVE-2012-3442related to CVE-2012-4520
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2012-3442 | 31 Jul 2012 | The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before… · fixed in 1.4.1 | First in chain | 16.3 |
| CVE-2012-4520 | 18 Nov 2012 | The django.http.HttpRequest.get_host function in Django 1.3.x before 1.3.4 and 1.4.x before 1.4.2 allows remote… · fixed in 1.4.2 | CVE-2012-3442 · related · High | 17.9 |
| CVE-2014-1418 | 16 May 2014 | Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1)… · fixed in 1.7b4 | CVE-2012-3442 · related · Medium | 17.0 |