First published: Fri Apr 08 2016(Updated: )
The `utils.http.is_safe_url function` in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks or possibly conduct cross-site scripting (XSS) attacks via a URL containing basic authentication, as demonstrated by `http://mysite.example.com\@attacker.com`.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | =1.8.9 | |
Djangoproject Django | =1.9 | |
Djangoproject Django | =1.9.1 | |
Djangoproject Django | =1.9.2 | |
pip/Django | >=1.9a1<1.9.3 | 1.9.3 |
pip/django | <1.8.10 | 1.8.10 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-2512 is classified as a high severity vulnerability due to its potential for facilitating phishing attacks and cross-site scripting.
You can fix CVE-2016-2512 by upgrading Django to versions 1.8.10 or 1.9.3 and above.
Django versions 1.8.9 and 1.9.0 to 1.9.2 are affected by CVE-2016-2512.
CVE-2016-2512 can allow remote attackers to redirect users, which can lead to phishing or potentially cross-site scripting attacks.
Yes, users of affected Django versions should be concerned until they apply the necessary updates to mitigate CVE-2016-2512.