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.
https://www.djangoproject.com/weblog/2011/sep/10/127/
https://www.djangoproject.com/weblog/2011/sep/09/
https://hermes.opensuse.org/messages/14700881
https://bugzilla.redhat.com/show_bug.cgi?id=737366
http://www.debian.org/security/2011/dsa-2332
http://secunia.com/advisories/46614
Published: 2011-10-19
Updated: 2025-04-11
Base Score: 6.8
Vector: CVSS2#AV:N/AC:M/Au:N/C:P/I:P/A:P
Severity: Medium
Base Score: 7.5
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Severity: High
Base Score: 8.7
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Severity: High
EPSS: 0.004