First published: Fri Oct 04 2013(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Django | >=1.5<1.5.2 | 1.5.2 |
pip/Django | >=1.4<1.4.6 | 1.4.6 |
Django | =1.4 | |
Django | =1.4.1 | |
Django | =1.4.2 | |
Django | =1.4.4 | |
Django | =1.4.5 | |
Django | =1.5 | |
Django | =1.5.1 | |
Django | =1.6-beta1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-6044 has a high severity rating because it can allow cross-site scripting (XSS) vulnerabilities in affected Django applications.
To fix CVE-2013-6044, upgrade to Django versions 1.4.6, 1.5.2, or higher.
CVE-2013-6044 affects Django versions 1.4.x before 1.4.6, 1.5.x before 1.5.2, and 1.6 beta 1.
CVE-2013-6044 can introduce cross-site scripting (XSS) vulnerabilities and potentially other security issues in Django applications.
There is no documented temporary workaround for CVE-2013-6044; the recommended action is to upgrade to a patched version.