CSRF in Djangoproject Django
CVE-2011-0696
- CVSS v2
- 6.8 Medium
- Public exploits
- None known
- EPSS
- 0.016 · 76.4th percentile
- Published
- 2011-02-14
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.
- Attack Vector
- Network
AV:N - Attack Complexity
- M
AC:M - Au
- N
Au:N - Confidentiality
- P
C:P - Integrity
- P
I:P - Availability
- P
A:P
EPSS exploit prediction
EPSS 0.016, 76.4th percentile (last changed ); unchanged over 30 days. About EPSS.
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)
- ADV-2011-0439 (vdb-entry)
- ADV-2011-0429 (vdb-entry)
- [oss-security] 20110209 Django multiple flaws (CVEs inside) (mailing-list, Patch)
- secunia.com/advisories/43230 (third-party-advisory)
- secunia.com/advisories/43426 (third-party-advisory)
- bugzilla.redhat.com/show_bug.cgi (Patch)
- ADV-2011-0372 (vdb-entry)
- FEDORA-2011-1261 (vendor-advisory)