{"id":"CVE-2011-4140","published":"2011-10-19T10:00:00Z","modified":"2024-08-07T00:01:51Z","title":"The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server…","vendor":null,"product":null,"tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.01093,"percentile":0.66276,"provenance":"source"},"cwes":[],"references":[{"url":"https://hermes.opensuse.org/messages/14700881","tags":["vendor-advisory","x_refsource_SUSE"]},{"url":"http://www.debian.org/security/2011/dsa-2332","tags":["vendor-advisory","x_refsource_DEBIAN"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=737366","tags":["x_refsource_CONFIRM"]},{"url":"http://secunia.com/advisories/46614","tags":["third-party-advisory","x_refsource_SECUNIA"]},{"url":"http://openwall.com/lists/oss-security/2011/09/11/1","tags":["mailing-list","x_refsource_MLIST"]},{"url":"https://www.djangoproject.com/weblog/2011/sep/10/127/","tags":["x_refsource_CONFIRM"]},{"url":"http://openwall.com/lists/oss-security/2011/09/13/2","tags":["mailing-list","x_refsource_MLIST"]},{"url":"https://www.djangoproject.com/weblog/2011/sep/09/","tags":["x_refsource_CONFIRM"]}],"priority":{"score":13.3,"factors":[{"name":"EPSS percentile","points":13.26}]},"affected":[{"ecosystem":"PyPI","package":"Django","vulnerableRanges":["<=1.2.7",">=1.3, <=1.3.1","<1.2.7",">=1.3, <1.3.1"],"patched":["1.2.7","1.3.1"],"from":["GHSA-h95j-h2rv-qrg4","PYSEC-2011-5"],"provenance":"source"}],"summary":{"text":"The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 fails to properly handle web-server configurations that accept arbitrary HTTP Host headers. An remote attacker can trigger unauthenticated forged requests using a DNS CNAME record and a web page containing JavaScript, with no authentication or network access required beyond getting victims to load that page.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:56:45Z"},"euvd":{"id":"EUVD-2011-0010","exploited":false,"provenance":"source"}}