Skip to content
Fencer Intel
high 7.4

CVE-2014-1418 json

Django Vulnerable to Cache Poisoning

published 12y ago modified 4mo ago also GHSA-q7q2-qf2q-rw3w , PYSEC-2014-19 , EUVD-2014-0008

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

Summary

Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attackers to obtain sensitive information or poison the cache via a request from certain browsers.

Patch / fix

  • pypi django 1.4.13, 1.5.8, 1.6.5, 1.7b4
  • python-django Debian 14, Debian 13, Debian 12 1.6.5-1

debian advisories DEBIAN-CVE-2014-1418

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

ubuntu advisories UBUNTU-CVE-2014-1418

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

Is CVE-2014-1418 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-1418 updated cvss 5.8

Django: cached data possibly served to the wrong session

  • Red Hat OpenStack Platform 3 Django Red Hat OpenStack Platform 4 Django Red Hat Subscription Asset Manager Django
    affected: no fix planned “Will not fix”

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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi django
>=1.4, <1.4.13
>=1.5, <1.5.8
>=1.6, <1.6.5
>=1.7a1, <1.7b4
>=1.7a0, <1.7b4
1.4.13
1.5.8
1.6.5
1.7b4

Classification

Weakness
  • CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
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.