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)
EPSS: 0.016 (73.1th percentile) — read the EPSS interpretation.
Affected products
- Djangoproject Django — versions 1.1, 1.1.0, 1.1.2
- N/a — versions n/a
Weakness classification (CWE)
References
- secalert@redhat.com (x_refsource_SECUNIA, third-party-advisory)
- secalert@redhat.com (x_refsource_SECUNIA, third-party-advisory)
- secalert@redhat.com (vdb-entry, x_refsource_VUPEN)
- secalert@redhat.com (vdb-entry, x_refsource_VUPEN)
- secalert@redhat.com (mailing-list, x_refsource_MLIST, Patch)
- secalert@redhat.com (x_refsource_SECUNIA, third-party-advisory)
- secalert@redhat.com (x_refsource_SECUNIA, third-party-advisory)
- secalert@redhat.com (x_refsource_CONFIRM, Patch)
- secalert@redhat.com (vdb-entry, x_refsource_VUPEN)
- secalert@redhat.com (vendor-advisory, x_refsource_FEDORA)