CVE-2014-3730PYSEC-2014-20GHSA-VQ3H-3Q7V-9PRW
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 before 1.7b4 does not pro
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.13, 1.5.8, 1.6.5, 1.7b4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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 before 1.7b4 does not properly validate URLs, which allows remote attackers to conduct open redirect attacks via a malformed URL, as demonstrated by "http:\\\djangoproject.com."
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- djangoPyPI
From 1.4 · fixed in 1.4.13; From 1.5 · fixed in 1.5.8; From 1.6 · fixed in 1.6.5; From 1.7a0 · fixed in 1.7b4
- djangoPyPI
From 1.4 · fixed in 1.4.13
- djangoPyPI
From 1.5 · fixed in 1.5.8
- djangoPyPI
From 1.6 · fixed in 1.6.5
- djangoPyPI
From 1.7a1 · fixed in 1.7b4