Django: Mitigated possible XSS attack via user-supplied redirect URLs
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-143-1 | python-django security update |
Debian DSA |
DSA-3151-1 | python-django security update |
EUVD |
EUVD-2015-0014 | The django.util.http.is_safe_url function in Django before 1.4.18, 1.6.x before 1.6.10, and 1.7.x before 1.7.3 does not properly handle leading whitespaces, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL, related to redirect URLs, as demonstrated by a \"\\njavascript:\" URL. |
Github GHSA |
GHSA-gv98-g628-m9x5 | Django Cross-site Scripting Vulnerability |
Ubuntu USN |
USN-2469-1 | Django vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.0% (3.042% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.