DescriptionThe 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.
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
|National Vulnerability Database|
SUSE Security Advisories:
- SUSE-SU-2014:0851-1, published Fri Jun 27 17:04:15 MDT 2014 openSUSE-SU-2014:1132-1
List of released packages
|Product(s)||Fixed package version(s)||References|
|SUSE OpenStack Cloud 3.0|| ||Patchnames: |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
|Products past their end of life and not receiving proactive updates anymore.|
|SUSE Cloud 2.0||python-django||Unsupported|
|SUSE Cloud 3||python-django||Released|
|SUSE Cloud 4||python-django||Unsupported|
|SUSE Cloud 4 Dependencies||python-django||Unsupported|
SUSE Timeline for this CVECVE page created: Wed Apr 23 19:16:11 2014
CVE page last modified: Thu Dec 7 13:07:02 2023