Django Reuses Cached CSRF Token
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-0473US | medium5.0 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2014-0456.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2014-0457.htmlWEB
- http://www.debian.org/security/2014/dsa-2934WEB
- http://www.ubuntu.com/usn/USN-2169-1WEB
- https://github.com/django/djangoPACKAGE
- https://github.com/django/django/commit/1170f285ddd6a94a65f911a27788ba49ca08c0b0WEB
- https://github.com/django/django/commit/6872f42757d7ef6a97e0b6ec5db4d2615d8a2bd8WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan