python-django: xss in is_safe_url function
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 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| OpenStack 3 for RHEL 6 | |||
| Django14-0:1.4.8-1.el6ost | cpe:/a:redhat:openstack:3::el6 | RHSA-2013:1521 | 2013-11-14T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2013-0009 | The is_safe_url function in utils/http.py in Django 1.4.x before 1.4.6, 1.5.x before 1.5.2, and 1.6 before beta 2 treats a URL's scheme as safe even if it is not HTTP or HTTPS, which might introduce cross-site scripting (XSS) or other vulnerabilities into Django applications that use this function, as demonstrated by \"the login view in django.contrib.auth.views\" and the javascript: scheme. |
Github GHSA |
GHSA-9cwg-mhxf-hh59 | Django cross-site scripting (XSS) vulnerability via is_safe_url function |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.3% (2.307% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.