high
7.5
CWE
352 264 200
Advisory Published
Advisory Published
Updated

CVE-2014-0473: CSRF

First published: Wed Apr 23 2014(Updated: )

The caching framework in Django before 1.4.11, 1.5.x before 1.5.6, 1.6.x before 1.6.3, and 1.7.x before 1.7 beta 2 reuses a cached CSRF token for all anonymous users, which allows remote attackers to bypass CSRF protections by reading the CSRF cookie for anonymous users.

Credit: security@debian.org

Affected SoftwareAffected VersionHow to fix
pip/Django>=1.6<1.6.3
1.6.3
pip/Django>=1.5<1.5.6
1.5.6
pip/django<1.4.11
1.4.11
Django=1.5
Django=1.5.1
Django=1.5.2
Django=1.5.3
Django=1.5.4
Django=1.5.5
Django=1.6
Django=1.6.1
Django=1.6.2
Django=1.7-alpha1
Django=1.7-alpha2
Django=1.7-beta1
Django<=1.4.10
Django=1.4
Django=1.4.1
Django=1.4.2
Django=1.4.3
Django=1.4.4
Django=1.4.5
Django=1.4.6
Django=1.4.7
Django=1.4.8
Django=1.4.9
Ubuntu=10.04
Ubuntu=12.04
Ubuntu=12.10
Ubuntu=13.10
Ubuntu=14.04
=1.5
=1.5.1
=1.5.2
=1.5.3
=1.5.4
=1.5.5
=1.6
=1.6.1
=1.6.2
=1.7-alpha1
=1.7-alpha2
=1.7-beta1
<=1.4.10
=1.4
=1.4.1
=1.4.2
=1.4.3
=1.4.4
=1.4.5
=1.4.6
=1.4.7
=1.4.8
=1.4.9
=10.04
=12.04
=12.10
=13.10
=14.04

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2014-0473?

    CVE-2014-0473 has a high severity rating due to its potential to allow remote attackers to bypass CSRF protections.

  • How do I fix CVE-2014-0473?

    To fix CVE-2014-0473, upgrade Django to version 1.4.11 or later, 1.5.6 or later, 1.6.3 or later, or any version from 1.7 beta 2 or later.

  • Which versions of Django are affected by CVE-2014-0473?

    Versions of Django affected by CVE-2014-0473 include 1.4 through 1.4.10, all 1.5.x versions prior to 1.5.6, all 1.6.x versions prior to 1.6.3, and 1.7-alpha and 1.7-beta1.

  • What are the implications of CVE-2014-0473?

    The implications of CVE-2014-0473 are that anonymous users could be targeted to bypass CSRF protections, potentially leading to unauthorized actions.

  • Is there a workaround for CVE-2014-0473?

    There are no specific workarounds for CVE-2014-0473; upgrading to a patched version is the recommended action.

Company

Resources

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