CVE-2014-0473: Django Reuses Cached CSRF Token
(updated )
The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to bypass CSRF protections by reading the CSRF cookie for anonymous users.
References
- github.com/advisories/GHSA-89hj-xfx5-7q66
- github.com/django/django
- github.com/django/django/commit/1170f285ddd6a94a65f911a27788ba49ca08c0b0
- github.com/django/django/commit/6872f42757d7ef6a97e0b6ec5db4d2615d8a2bd8
- github.com/django/django/commit/d63e20942f3024f24cb8cd85a49461ba8a9b6736
- github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2014-2.yaml
- nvd.nist.gov/vuln/detail/CVE-2014-0473
- www.djangoproject.com/weblog/2014/apr/21/security
Code Behaviors & Features
Detect and mitigate CVE-2014-0473 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →