Skip to content
Fencer Intel
high 7.5

CVE-2014-0473 json

Django Reuses Cached CSRF Token

published 12y ago modified 4mo ago also GHSA-89hj-xfx5-7q66 , PYSEC-2014-2 , EUVD-2014-0009

cvss
7.5
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi django 1.4.11, 1.5.6, 1.6.3
  • python-django Debian 14, Debian 13, Debian 12 1.6.3-1

debian advisories DEBIAN-CVE-2014-0473

  • python-django Ubuntu 14.04 LTS 1.6.1-2ubuntu0.1

ubuntu advisories UBUNTU-CVE-2014-0473

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • Django14 openstack 4, openstack 3 1.4.11-1.el6ost

red hat advisories RHSA-2014:0457RHSA-2014:0456

Is CVE-2014-0473 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0473 updated cvss 4.3

python-django: caching of anonymous pages could reveal CSRF token

  • Red Hat Subscription Asset Manager Django
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux OpenStack Platform 3.0 Django14 1.4.11-1.el6ost
    fixed: vendor fix RHSA-2014:0457
  • Red Hat Enterprise Linux OpenStack Platform 4.0 Django14 1.4.11-1.el6ost
    fixed: vendor fix RHSA-2014:0456

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi django
<1.4.11
>=1.5, <1.5.6
>=1.6, <1.6.3
1.4.11
1.5.6
1.6.3

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.