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
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 01:31
Type | Values Removed | Values Added |
---|---|---|
References | () http://openwall.com/lists/oss-security/2011/09/11/1 - Patch | |
References | () http://openwall.com/lists/oss-security/2011/09/13/2 - Patch | |
References | () http://secunia.com/advisories/46614 - | |
References | () http://www.debian.org/security/2011/dsa-2332 - | |
References | () https://bugzilla.redhat.com/show_bug.cgi?id=737366 - Patch | |
References | () https://hermes.opensuse.org/messages/14700881 - | |
References | () https://www.djangoproject.com/weblog/2011/sep/09/ - Patch, Vendor Advisory | |
References | () https://www.djangoproject.com/weblog/2011/sep/10/127/ - Patch |
Information
Published : 2011-10-19 10:55
Updated : 2024-11-21 01:31
NVD link : CVE-2011-4140
Mitre link : CVE-2011-4140
CVE.ORG link : CVE-2011-4140
JSON object : View
Products Affected
djangoproject
- django
CWE
CWE-352
Cross-Site Request Forgery (CSRF)