Vulnerabilities · 2011 · Djangoproject
CVE-2011-4139
Djangoproject Django vulnerability
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.
Affected products
Django. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Djangoproject Django runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.djangoproject.com/weblog/2011/sep/09/ · Patch
- openwall.com/lists/oss-security/2011/09/11/1 · Patch
- openwall.com/lists/oss-security/2011/09/13/2 · Patch
- bugzilla.redhat.com/show_bug.cgi?id=737366 · Patch
- www.djangoproject.com/weblog/2011/sep/10/127/ · Patch
- secunia.com/advisories/46614
- www.debian.org/security/2011/dsa-2332
- hermes.opensuse.org/messages/14700881
- nvd.nist.gov/vuln/detail/CVE-2011-4139
- cve.org/CVERecord?id=CVE-2011-4139
More vulnerabilities in Djangoproject products
CVE-2026-1312CVE-2026-1287CVE-2026-1285CVE-2026-1207CVE-2025-64460CVE-2025-64459CVE-2025-64458CVE-2025-59682All 137
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.