First published: Mon Oct 03 2016(Updated: )
The cookie parsing code in Django before 1.8.15 and 1.9.x before 1.9.10, when used on a site with Google Analytics, allows remote attackers to bypass an intended CSRF protection mechanism by setting arbitrary cookies.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/django | >=1.9<1.9.10 | 1.9.10 |
pip/django | <1.8.15 | 1.8.15 |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
djangoproject Django | <=1.8.14 | |
djangoproject Django | =1.9.0 | |
djangoproject Django | =1.9.1 | |
djangoproject Django | =1.9.2 | |
djangoproject Django | =1.9.3 | |
djangoproject Django | =1.9.4 | |
djangoproject Django | =1.9.5 | |
djangoproject Django | =1.9.6 | |
djangoproject Django | =1.9.7 | |
djangoproject Django | =1.9.8 | |
djangoproject Django | =1.9.9 | |
Debian | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-7401 is classified as a high-severity vulnerability due to its ability to bypass CSRF protections.
To fix CVE-2016-7401, update your Django installation to version 1.9.10 or 1.8.15.
CVE-2016-7401 affects Django versions prior to 1.8.15 and 1.9.x before 1.9.10.
Yes, CVE-2016-7401 can significantly impact your web application's security by allowing remote attackers to bypass CSRF protections.
The recommended course of action for CVE-2016-7401 is to upgrade Django to the fixed versions rather than using a workaround.