CVE-2015-2317PYSEC-2015-9GHSA-7FQ8-4PV5-5W5C
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 before 1.8c1 does not
- 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.20, 1.6.11, 1.7.7, 1.8c1
- 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 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 before 1.8c1 does not properly validate URLs, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a control character in a URL, as demonstrated by a \x08javascript: URL.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- djangoPyPI
fixed in 1.4.20; From 1.5 · fixed in 1.6.11; From 1.7 · fixed in 1.7.7; From 1.8a0 · fixed in 1.8c1
- djangoPyPI
fixed in 1.4.20
- djangoPyPI
From 1.5 · fixed in 1.6.11
- djangoPyPI
From 1.7 · fixed in 1.7.7
- djangoPyPI
From 1.8a1 · fixed in 1.8c1