CVE-2011-4140
- State
- Published
- Severity
- Not scored
- Published
- Oct 19, 2011
- Updated
- Aug 7, 2024
- Reserved
- Oct 19, 2011
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.
Scores
The record has no CVSS score.
Weaknesses
The record names no weakness.
Affected Products
| Product | Versions |
|---|---|
n/an/a |
|
References
- openSUSE-SU-2012:0653vendor-advisory
- DSA-2332vendor-advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=737366
- 46614third-party-advisory
- [oss-security] 20110911 CVE Request -- Django: v1.3.1, v1.2.7 multiple security flawsmailing-list
- https://www.djangoproject.com/weblog/2011/sep/10/127/
- [oss-security] 20110913 Re: CVE Request -- Django: v1.3.1, v1.2.7 multiple security flawsmailing-list
- https://www.djangoproject.com/weblog/2011/sep/09/
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.