CVE-2011-4140

Severity: medium (CVSS 6.8 v2.0)
Exploited in the wild: not listed in CISA KEV
EPSS: 1.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2011-10-19 · updated 2026-06-16
Weakness: CWE-352

Description

The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.

Affected products

Django: through 1.2.6; 0.91, 0.95, 0.95.1, 0.96, 1.0, 1.0.1 (+15)

References

http://openwall.com/lists/oss-security/2011/09/11/1
http://openwall.com/lists/oss-security/2011/09/13/2
http://secunia.com/advisories/46614
http://www.debian.org/security/2011/dsa-2332
https://bugzilla.redhat.com/show_bug.cgi?id=737366
https://hermes.opensuse.org/messages/14700881
https://www.djangoproject.com/weblog/2011/sep/09/
https://www.djangoproject.com/weblog/2011/sep/10/127/
http://openwall.com/lists/oss-security/2011/09/11/1
http://openwall.com/lists/oss-security/2011/09/13/2
http://secunia.com/advisories/46614
http://www.debian.org/security/2011/dsa-2332

Get alerted when CVE-2011-4140 or the next vulnerability affects your stack