Description (CNA)
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 (CNA)
| Vendor / product | Versions |
|---|---|
| n/a / n/a | affected n/a |
CWE
No CWE identifiers supplied.
References
- https://hermes.opensuse.org/messages/14700881
- http://www.debian.org/security/2011/dsa-2332
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- http://secunia.com/advisories/46614
- http://openwall.com/lists/oss-security/2011/09/11/1
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://openwall.com/lists/oss-security/2011/09/13/2
- https://www.djangoproject.com/weblog/2011/sep/09/
ADP enrichment
No English description supplied.
- https://hermes.opensuse.org/messages/14700881
- http://www.debian.org/security/2011/dsa-2332
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- http://secunia.com/advisories/46614
- http://openwall.com/lists/oss-security/2011/09/11/1
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- http://openwall.com/lists/oss-security/2011/09/13/2
- https://www.djangoproject.com/weblog/2011/sep/09/