Django up to 1.7 Cache Framework access control

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in Django. The impacted element is an unknown function of the component Cache Framework. Such manipulation leads to access control. This vulnerability is traded as CVE-2014-0473. Furthermore, there is an exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Django (Content Management System) and classified as problematic. Affected by this issue is some unknown functionality of the component Cache Framework. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality. CVE summarizes:

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.

The weakness was shared 04/21/2014 by Paul McMillan as Security releases issued as confirmed advisory (Website). The advisory is shared for download at djangoproject.com. The vendor cooperated in the coordination of the public release. This vulnerability is handled as CVE-2014-0473 since 12/19/2013. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but an exploit is available. The MITRE ATT&CK project declares the attack technique as T1068. The advisory points out:

The caching framework includes an option to cache responses to anonymous (i.e., unauthenticated) clients. When the first anonymous request to a given page is by a client which did not have a CSRF cookie, the cache framework will also cache the CSRF cookie and serve the same nonce to other anonymous clients who do not have a CSRF cookie. This can allow an attacker to obtain a valid CSRF cookie value and perform attacks which bypass the check for the cookie.

It is declared as highly functional. The vulnerability scanner Nessus provides a plugin with the ID 74097 (Debian DSA-2934-1 : python-django - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 123242 (Fedora Security Update for python-django14 (FEDORA-2015-0804)). The advisory illustrates:

Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: 1) One or more views are present which construct a URL based on user input (commonly, a "next" parameter in a querystring indicating where to redirect upon successful completion of an action). 2) One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing.

Upgrading to version 1.4.11, 1.5.6 or 1.6.3 eliminates this vulnerability. The upgrade is hosted for download at djangoproject.com. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:

To remedy this, the caching framework will no longer cache such responses. The heuristic for this will be: 1) If the incoming request did not submit any cookies, and 2) If the response did send one or more cookies, and 3) If the Vary: Cookie header is set on the response, then the response will not be cached.

The vulnerability is also documented in the databases at X-Force (92706), Tenable (74097), SecurityFocus (BID 67040†), Secunia (SA58201†) and SecurityTracker (ID 1030149†). The entries VDB-10295, VDB-13065, VDB-13063 and VDB-13240 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Highly functional

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74097
Nessus Name: Debian DSA-2934-1 : python-django - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 702934
OpenVAS Name: Debian Security Advisory DSA 2934-1 (python-django - security update
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Django 1.4.11/1.5.6/1.6.3

Timelineinfo

12/19/2013 🔍
04/21/2014 +123 days 🔍
04/21/2014 +0 days 🔍
04/21/2014 +0 days 🔍
04/23/2014 +2 days 🔍
04/23/2014 +0 days 🔍
04/23/2014 +0 days 🔍
04/23/2014 +0 days 🔍
04/24/2014 +1 days 🔍
06/08/2014 +45 days 🔍
06/17/2021 +2566 days 🔍

Sourcesinfo

Advisory: Security releases issued
Researcher: Paul McMillan
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2014-0473 (🔍)
GCVE (CVE): GCVE-0-2014-0473
GCVE (VulDB): GCVE-100-13064

OVAL: 🔍

X-Force: 92706 - Django cross-site request forgery, Medium Risk
SecurityFocus: 67040 - Django CVE-2014-0473 Cross Site Request Forgery Vulnerability
Secunia: 58201 - Django Security Issue and Multiple Vulnerabilities, Moderately Critical
SecurityTracker: 1030149 - Django Bugs Let Remote Users Execute Arbitrary Code, Modify SQL Queries, and Obtain Potentially Sensitive Information
Vulnerability Center: 44799 - Django <1.4.11, 1.5 - 1.5.5, 1.6 - 1.6.2, 1.7 - 1.7 beta 1 Remote CSRF Vulnerability, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 04/23/2014 16:59
Updated: 06/17/2021 16:49
Changes: 04/23/2014 16:59 (89), 05/30/2017 09:13 (6), 06/17/2021 16:49 (3)
Complete: 🔍
Cache ID: 216:9E3:103

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!