Severity
Severity not reported.
Affected versions
No affected versions listed.
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.
References
- Advisorysecunia.com/advisories/46614 ↗
- Advisorywww.debian.org/security/2011/dsa-2332 ↗
- Advisorywww.djangoproject.com/weblog/2011/sep/09/ ↗
- Fixopenwall.com/lists/oss-security/2011/09/11/1 ↗
- Fixopenwall.com/lists/oss-security/2011/09/13/2 ↗
- Fixbugzilla.redhat.com/show_bug.cgi?id=737366 ↗
- Fixwww.djangoproject.com/weblog/2011/sep/09/ ↗
- Fixwww.djangoproject.com/weblog/2011/sep/10/127/ ↗
- Webhermes.opensuse.org/messages/14700881 ↗