CWE
20 352
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2011-4136: Input Validation

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 SoftwareAffected VersionHow 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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2011-4136?

    CVE-2011-4136 is rated as low severity due to the limited scope of the vulnerability.

  • How do I fix CVE-2011-4136?

    To fix CVE-2011-4136, upgrade Django to version 1.2.7 or 1.3.1 or later.

  • What versions of Django are affected by CVE-2011-4136?

    CVE-2011-4136 affects Django versions prior to 1.2.7 and 1.3.x prior to 1.3.1.

  • Can CVE-2011-4136 allow session hijacking?

    Yes, CVE-2011-4136 can potentially allow attackers to hijack sessions due to improper session key handling.

  • Is CVE-2011-4136 related to cache implementation in Django?

    Yes, CVE-2011-4136 involves issues with session data stored in the cache using root namespace for session identifiers.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203