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.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2014-0473 from the MITRE CVE dictionary dictionary and NIST NVD.
| Base Score | 4.3 |
|---|---|
| Base Metrics | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| Access Vector | Network |
| Access Complexity | Medium |
| Authentication | None |
| Confidentiality Impact | None |
| Integrity Impact | Partial |
| Availability Impact | None |
Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).
| Platform | Errata | Release Date |
|---|---|---|
| Red Hat Enterprise Linux OpenStack Platform 4.0 (Django14) | RHSA-2014:0456 | 2014-04-30 |
| Red Hat Enterprise Linux OpenStack Platform 3.0 (Django14) | RHSA-2014:0457 | 2014-04-30 |
| Platform | Package | State |
|---|---|---|
| Red Hat Subscription Asset Manager 1 | Django | Will not fix |
| Red Hat Enterprise Linux OpenStack Platform 4.0 | Django | Will not fix |
| Red Hat Enterprise Linux OpenStack Platform 3.0 | Django | Will not fix |
Vulmon