CSRF in Djangoproject Django
CVE-2011-0696
Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a "combination of browser plugins and redirects," a related issue to CVE-2011-0447.
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.016 (75.0th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 75th percentile — 75.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.016 · newest: 0.016 · change: 0.000
Affected products
- Djangoproject Django — versions 1.1, 1.1.0, 1.1.2
Weakness classification (CWE)
References
- secunia.com/advisories/43297 (third-party-advisory)
- secunia.com/advisories/43382 (third-party-advisory)
- www.vupen.com/english/advisories/2011/0439 (vdb-entry)
- www.vupen.com/english/advisories/2011/0429 (vdb-entry)
- openwall.com/lists/oss-security/2011/02/09/6 (mailing-list, Patch)
- secunia.com/advisories/43230 (third-party-advisory)
- secunia.com/advisories/43426 (third-party-advisory)
- bugzilla.redhat.com/show_bug.cgi (Patch)
- www.vupen.com/english/advisories/2011/0372 (vdb-entry)
- lists.fedoraproject.org/pipermail/package-announce/2011-February/054207.html (vendor-advisory)