CSRF in Djangoproject Django
CVE-2011-4140
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v2 metric
CVSS v2 base score 6.8 (Medium). Vector: AV:N/AC:M/Au:N/C:P/I:P/A:P. This CVE predates CVSS v3 and has no v3 score from NVD.
EPSS exploit prediction
EPSS: 0.011 (64.2th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 64th percentile — 64.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.011 · newest: 0.011 · change: 0.000
Affected products
- Djangoproject Django — versions 0.91, 0.95, 0.95.1
Weakness classification (CWE)
References
- hermes.opensuse.org/messages/14700881 (vendor-advisory)
- www.debian.org/security/2011/dsa-2332 (vendor-advisory)
- bugzilla.redhat.com/show_bug.cgi (Patch)
- secunia.com/advisories/46614 (third-party-advisory)
- openwall.com/lists/oss-security/2011/09/11/1 (mailing-list, Patch)
- www.djangoproject.com/weblog/2011/sep/10/127/ (Patch)
- openwall.com/lists/oss-security/2011/09/13/2 (mailing-list, Patch)
- www.djangoproject.com/weblog/2011/sep/09/ (Patch, Vendor Advisory)