CVE-2011-4136 Session manipulation in Django

Medium 5.8 Published Updated

Remote attackers can modify user sessions by exploiting a namespace collision in Django's cache-based session storage, requiring cache backend configuration.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2011-4136?

CVE-2011-4136 is a medium-severity vulnerability in Djangoproject Django, published on 19 Oct 2011. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.

Weakness: CWE-20

Which versions are affected by CVE-2011-4136?

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

PackageAffectedFixed in
django PyPIAll versions1.2.7, 1.3.1
django PyPIAll versions1.2.7
django PyPIFrom 1.31.3.1
Django PyPIAll versions1.2.7
Django PyPIFrom 1.31.3.1

Products include Djangoproject Django.

How do I fix CVE-2011-4136?

Upgrade django to a fixed version for your release line: 1.2.7 or 1.3.1.

Is CVE-2011-4136 being exploited?

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

All Djangoproject Django vulnerabilities

Sources

Also known as DEBIAN-CVE-2011-4136, GHSA-x88j-93vc-wpmp, PYSEC-2011-1.

Is CVE-2011-4136 in your software?

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

Check your SBOMs for free