CVE-2011-4139 Django Vulnerable to Cache Poisoning
Remote attackers can poison caches by manipulating the HTTP Host header in Django applications, potentially serving malicious content to users.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2011-4139?
CVE-2011-4139 is a medium-severity vulnerability in Djangoproject Django, published on 19 Oct 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's HTTP Host header to construct a full URL in certain circumstances, which allows remote attackers to conduct cache poisoning attacks via a crafted request.
Weakness: CWE-20
Which versions are affected by CVE-2011-4139?
5 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django PyPI | All versions | 1.2.7, 1.3.1 |
django PyPI | All versions | 1.2.7 |
django PyPI | From 1.3 | 1.3.1 |
Django PyPI | All versions | 1.2.7 |
Django PyPI | From 1.3 | 1.3.1 |
Products include Djangoproject Django.
How do I fix CVE-2011-4139?
Upgrade django to a fixed version for your release line: 1.2.7 or 1.3.1.
Is CVE-2011-4139 being exploited?
There is no known exploitation of CVE-2011-4139 in the wild and no public exploit code.
Other vulnerabilities in Djangoproject Django
- CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin
- CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle
- CVE-2024-42005 Django SQL injection vulnerability
- CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files
- CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
Sources
Also known as DEBIAN-CVE-2011-4139, GHSA-rm2j-x595-q9cj, PYSEC-2011-4.