GHSA-q7q2-qf2q-rw3w CVE-2014-1418 PYSEC-2014-19

Django Vulnerable to Cache Poisoning

High PyPI

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 2.57%; Chance of exploitation in the next 30 days. Higher than 85.14% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-349 Acceptance of Extraneous Untrusted Data With Trusted Data
Fix: 1.4.13; Upgrade django to this version or later

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.

Affected versions

PyPI

Package	Vulnerable	Fixed in
django	`>= 1.4, < 1.4.13`	`1.4.13`
django	`>= 1.5, < 1.5.8`	`1.5.8`
django	`>= 1.6, < 1.6.5`	`1.6.5`
django	`>= 1.7a1, < 1.7b4`	`1.7b4`
django	`>= 1.4, < 1.4.13` `>= 1.5, < 1.5.8` `>= 1.6, < 1.6.5` `>= 1.7a0, < 1.7b4`	`1.4.13` `1.5.8` `1.6.5` `1.7b4`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

django PyPI → `1.4.13`

pip

pip install --upgrade "django>=1.4.13"

poetry

poetry add "django>=1.4.13"

uv

uv add "django>=1.4.13"

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack vector: Network
Attack complexity: Low
Attack requirements: Present
Privileges required: None
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): High
Availability (vulnerable system): None
Confidentiality (subsequent systems): None
Integrity (subsequent systems): None
Availability (subsequent systems): None

CVSS 3.1 7.4

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Weakness

CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data

The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

References

Advisories

Write-ups

djangoproject.com/weblog/2014/may/14/security-releases-issued

Packages

github.com/django/django

Timeline

May 16, 2014 Published
Jun 10, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-q238-5cxm-5c9h Django GeoDjango vulnerable to denial of service through deeply nested geometry collections	Medium	Also affects django
GHSA-wvqv-fj8w-qmhm Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing	High	Also affects django
GHSA-8qcx-xf44-272x Django: DomainNameValidator permits newline characters that may enable HTTP header injection	Medium	Also affects django
GHSA-crhf-3pfg-w68w Django: GDALRaster may over-read heap memory when constructed from bytes	Medium	Also affects django
GHSA-3h9f-r86x-qvjx Django: cache middleware may expose private responses when unrelated request cookies are present	Medium	Also affects django
GHSA-8cjm-8mp7-r2xf Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling	Medium	Also affects django
GHSA-mm6v-q8q9-pgcf Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake	Low	Also affects django
GHSA-h7pc-vwp9-298g Django: signed cookies are vulnerable to salt namespace collisions	Medium	Also affects django

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor