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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- http://www.securityfocus.com/bid/61777 ↗
- http://www.securitytracker.com/id/1028915 ↗
- http://lists.opensuse.org/opensuse-updates/2013-10/msg00015.html ↗
- https://github.com/django/django/commit/ec67af0bd609c412b76eaa4cc89968a2a8e5ad6a ↗
- http://secunia.com/advisories/54476 ↗
- http://rhn.redhat.com/errata/RHSA-2013-1521.html ↗
- http://seclists.org/oss-sec/2013/q3/369 ↗
- https://www.djangoproject.com/weblog/2013/aug/13/security-releases-issued ↗
- https://exchange.xforce.ibmcloud.com/vulnerabilities/86437 ↗
- https://github.com/django/django/commit/ae3535169af804352517b7fea94a42a1c9c4b762 ↗
- https://github.com/django/django/commit/1a274ccd6bc1afbdac80344c9b6e5810c1162b5f ↗
- http://seclists.org/oss-sec/2013/q3/411 ↗
- http://www.debian.org/security/2013/dsa-2740 ↗