ChainPyPI:Django
Django: related fixes (2014–2017)
4 CVEs over 4 generations, 16 May 2014 to 4 Apr 2017.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2014-373016 May 2014 First in the chain
- CVE-2015-231725 Mar 2015 related to CVE-2014-3730
- CVE-2016-25128 Apr 2016 related to CVE-2014-3730related to CVE-2015-2317
- CVE-2017-72334 Apr 2017 related to CVE-2014-3730related to CVE-2015-2317and 1 more
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-2014-3730 | 16 May 2014 | The django.util.http.is_safe_url function in Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7… · fixed in 1.7b4 | First in chain | 17.6 |
| CVE-2015-2317 | 25 Mar 2015 | The utils.http.is_safe_url function in Django before 1.4.20, 1.5.x, 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x… · fixed in 1.8c1 | CVE-2014-3730 · related · Medium | 18.4 |
| CVE-2016-2512 | 8 Apr 2016 | The utils.http.is_safe_url function in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to redirect… · fixed in 1.9.3 | CVE-2014-3730 · related · Medium | 18.1 |
| CVE-2017-7233 | 4 Apr 2017 | Django 1.10 before 1.10.7, 1.9 before 1.9.13, and 1.8 before 1.8.18 relies on user input in some cases to redirect the… · fixed in 1.10.7 | CVE-2014-3730 · related · Medium | 16.8 |