Upstream information
Description
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.SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
National Vulnerability Database | |
---|---|
Base Score | 5 |
Vector | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Access Vector | Network |
Access Complexity | Low |
Authentication | None |
Confidentiality Impact | Partial |
Integrity Impact | None |
Availability Impact | None |
- SUSE-SU-2014:0851-1, published Fri Jun 27 17:04:15 MDT 2014
- openSUSE-SU-2014:1132-1, published Tue, 16 Sep 2014 15:04:18 +0200 (CEST)
List of released packages
Product(s) | Fixed package version(s) | References |
---|---|---|
SUSE OpenStack Cloud 3.0 |
| Patchnames: sleclo30sp3-python-django |
openSUSE 13.1 |
| Patchnames: openSUSE-2014-542 |
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.
Product(s) | Source package | State |
---|---|---|
SUSE Cloud 2.0 | python-django | Affected |
SUSE Cloud 3 | python-django | Released |
SUSE Cloud 4 | python-django | Affected |
SUSE Cloud 4 Dependencies | python-django | Affected |