CVE-2014-1418

CVE-2014-1418 is a medium-severity vulnerability in Djangoproject Django with a CVSS 2.0 base score of 6.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Description

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.

Frequently asked questions

What is CVE-2014-1418?
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.
How severe is CVE-2014-1418?
CVE-2014-1418 has a CVSS 2.0 base score of 6.4, rated medium severity.
Is CVE-2014-1418 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2014-1418?
CVE-2014-1418 primarily affects Djangoproject Django. In total, 39 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2014-1418?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2014-1418 published?
CVE-2014-1418 was published on 2014-05-16 and last updated on 2026-06-17.

References

Affected products (39)

More vulnerabilities in Djangoproject Django

All CVEs affecting Djangoproject Django →