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.
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Link | Tags |
---|---|
https://hermes.opensuse.org/messages/14700881 | vendor advisory |
http://www.debian.org/security/2011/dsa-2332 | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=737366 | patch |
http://secunia.com/advisories/46614 | third party advisory |
http://openwall.com/lists/oss-security/2011/09/11/1 | mailing list patch |
https://www.djangoproject.com/weblog/2011/sep/10/127/ | patch |
http://openwall.com/lists/oss-security/2011/09/13/2 | mailing list patch |
https://www.djangoproject.com/weblog/2011/sep/09/ | patch vendor advisory |