CVE-2011-0696 Cross-site request forgery in Django

Medium 6.8 Published Updated

Remote attackers can bypass CSRF protections in Django applications by forging AJAX requests, potentially allowing unauthorized actions on behalf of authenticated users.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2011-0696?

CVE-2011-0696 is a medium-severity vulnerability in Djangoproject Django, published on 14 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-352

Which versions are affected by CVE-2011-0696?

5 open source packages ship an affected version, including django and Django. It affects 1 product.

PackageAffectedFixed in
django PyPIFrom 1.11.1.4, 1.2.5
django PyPIFrom 1.11.1.4
django PyPIFrom 1.21.2.5
Django PyPIFrom 1.11.1.4
Django PyPIFrom 1.21.2.5

Products include Djangoproject Django.

How do I fix CVE-2011-0696?

Upgrade django to a fixed version for your release line: 1.1.4 or 1.2.5.

Is CVE-2011-0696 being exploited?

There is no known exploitation of CVE-2011-0696 in the wild and no public exploit code.

All Djangoproject Django vulnerabilities

Sources

Also known as DEBIAN-CVE-2011-0696, GHSA-5j2h-h5hg-3wf8, PYSEC-2011-10.

Is CVE-2011-0696 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free