Strix
26.1K

CVE-2011-4136

UnknownEPSS 2.28%

Last modified

CVE-2011-4136 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.28% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
2.28%

80.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
DjangoprojectDjango<= 1.2.6
DjangoprojectDjango0.91
DjangoprojectDjango0.95
DjangoprojectDjango0.95.1
DjangoprojectDjango0.96
DjangoprojectDjango1.0
DjangoprojectDjango1.0.1
DjangoprojectDjango1.0.2
DjangoprojectDjango1.1
DjangoprojectDjango1.1.0
DjangoprojectDjango1.1.2
DjangoprojectDjango1.1.3
DjangoprojectDjango1.2
DjangoprojectDjango1.2.1
DjangoprojectDjango1.2.2
DjangoprojectDjango1.2.3
DjangoprojectDjango1.2.4
DjangoprojectDjango1.2.5
DjangoprojectDjango1.3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2011-4136?
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.
How severe is CVE-2011-4136?
Severity scoring for CVE-2011-4136 is pending analysis. The EPSS model estimates a 2.28% probability of exploitation in the next 30 days.
How do I fix CVE-2011-4136?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2011-4136?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST