Severity
Severity not reported.
Affected versions
| Affected | Fixed |
|---|---|
| GIT github.com/django/django ↗ | |
| All commits before ec67af0bd609c412b76eaa4cc89968a2a8e5ad6a | Commit ec67af0bd609c412b76eaa4cc89968a2a8e5ad6a |
| Not specified | Commit ae3535169af804352517b7fea94a42a1c9c4b762 |
| Not specified | Commit 1a274ccd6bc1afbdac80344c9b6e5810c1162b5f |
1.4 to before 1.4.6 | 1.4.6Advisories → |
1.5 to before 1.5.2 | 1.5.2Advisories → |
Description
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.
References
- Webwww.securitytracker.com/id/1028915 ↗
- ARTICLEwww.djangoproject.com/weblog/2013/aug/13/security-releases-issued ↗
- Webseclists.org/oss-sec/2013/q3/369 ↗
- Fixgithub.com/django/django/commit/ec67af0bd609c412b76eaa4cc89968a2a8e5ad6a ↗
- Fixgithub.com/django/django/commit/ae3535169af804352517b7fea94a42a1c9c4b762 ↗
- Fixgithub.com/django/django/commit/1a274ccd6bc1afbdac80344c9b6e5810c1162b5f ↗
- Webseclists.org/oss-sec/2013/q3/411 ↗
- Webwww.securityfocus.com/bid/61777 ↗
- Advisorysecunia.com/advisories/54476 ↗
- Advisoryrhn.redhat.com/errata/RHSA-2013-1521.html ↗
- Weblists.opensuse.org/opensuse-updates/2013-10/msg00015.html ↗
- Webexchange.xforce.ibmcloud.com/vulnerabilities/86437 ↗
- Advisorywww.debian.org/security/2013/dsa-2740 ↗
- Advisorygithub.com/advisories/GHSA-9cwg-mhxf-hh59 ↗