CVE-2014-0473
N/A
Published: April 23, 2014 at 02:00 PM UTC
Updated: June 17, 2026 at 12:03 AM UTC
2 products affected across 2 vendorsUbuntu LinuxDjango
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%
Description
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (7)
Vendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-updates/2014-09/msg00023.htmlVendor Advisoryx_refsource_REDHAT
Source: [email protected]
http://rhn.redhat.com/errata/RHSA-2014-0456.htmlVendor Advisoryx_refsource_REDHAT
Source: [email protected]
http://rhn.redhat.com/errata/RHSA-2014-0457.htmlVendor Advisoryx_refsource_DEBIAN
Source: [email protected]
http://www.debian.org/security/2014/dsa-2934x_refsource_CONFIRMVendor Advisory
Source: [email protected]
https://www.djangoproject.com/weblog/2014/apr/21/security/Quick Info
StatusMODIFIED
CWE
CWE-264
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card