First published: Sun Sep 11 2011(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Djangoproject Django | <=1.2.6 | |
Djangoproject Django | =1.2.5 | |
Djangoproject Django | =0.95 | |
Djangoproject Django | =1.0 | |
Djangoproject Django | =1.3 | |
Djangoproject Django | =1.1.2 | |
Djangoproject Django | =1.0.1 | |
Djangoproject Django | =1.1 | |
Djangoproject Django | =1.2.1 | |
Djangoproject Django | =1.2.4 | |
Djangoproject Django | =0.91 | |
Djangoproject Django | =1.0.2 | |
Djangoproject Django | =1.2.3 | |
Djangoproject Django | =1.3-alpha1 | |
Djangoproject Django | =1.1.3 | |
Djangoproject Django | =1.2.1-2 | |
Djangoproject Django | =1.2 | |
Djangoproject Django | =0.95.1 | |
Djangoproject Django | =0.96 | |
Djangoproject Django | =1.3-alpha2 | |
Djangoproject Django | =1.1.0 | |
Djangoproject Django | =1.2.2 | |
pip/Django | >=1.3<1.3.1 | 1.3.1 |
pip/Django | >=0<1.2.7 | 1.2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2011-4136 is rated as low severity due to the limited scope of the vulnerability.
To fix CVE-2011-4136, upgrade Django to version 1.2.7 or 1.3.1 or later.
CVE-2011-4136 affects Django versions prior to 1.2.7 and 1.3.x prior to 1.3.1.
Yes, CVE-2011-4136 can potentially allow attackers to hijack sessions due to improper session key handling.
Yes, CVE-2011-4136 involves issues with session data stored in the cache using root namespace for session identifiers.