Django up to 1.7 Cache information disclosure

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.
3.6$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Django. This impacts an unknown function of the component Cache Handler. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2014-1418. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Django (Content Management System) and classified as problematic. This issue affects some unknown functionality of the component Cache Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attackers to obtain sensitive information or poison the cache via a request from certain browsers.

The weakness was presented 05/13/2014 by Michael Nelson, Natalia Bidart and James Westby as Bug 1097500 as confirmed bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. The public release was coordinated in cooperation with the project team. The identification of this vulnerability is CVE-2014-1418 since 01/13/2014. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue. The advisory points out:

In certain situations, Django may allow caches to store private data related to a particular session and then serve that data to requests with a different session, or no session at all. This can both lead to information disclosure, and can be a vector for cache poisoning. When using Django sessions, Django will set a ``Vary: Cookie`` header to ensure caches do not serve cached data to requests from other sessions. However, older versions of Internet Explorer (most likely only Internet Explorer 6, and Internet Explorer 7 if run on Windows XP or Windows Server 2003) are unable to handle the ``Vary`` header in combination with many content types. Therefore, Django would remove the header if the request was made by Internet Explorer.

The vulnerability scanner Nessus provides a plugin with the ID 74178 (Fedora 20 : python-django14-1.4.13-1.fc20 (2014-6442)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora 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)).

Upgrading to version 1.4.13, 1.5.8, 1.6.5 or 1.7 beta 4 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The bug report contains the following remark:

To remedy this, the special behavior for these older Internet Explorer versions has been removed, and the ``Vary`` header is no longer stripped from the response. In addition, modifications to the ``Cache-Control`` header for all Internet Explorer requests with a ``Content-Disposition`` header, have also been removed as they were found to have similar issues.

The vulnerability is also documented in the databases at X-Force (93179), Tenable (74178), SecurityFocus (BID 67408†), OSVDB (107011†) and Secunia (SA61281†). See VDB-13065, VDB-13064, VDB-13240 and VDB-67424 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.6

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 74178
Nessus Name: Fedora 20 : python-django14-1.4.13-1.fc20 (2014-6442)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍

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.13/1.5.8/1.6.5/1.7 beta 4

Timelineinfo

01/13/2014 🔍
05/13/2014 +120 days 🔍
05/13/2014 +0 days 🔍
05/15/2014 +2 days 🔍
05/15/2014 +0 days 🔍
05/16/2014 +1 days 🔍
05/20/2014 +4 days 🔍
05/26/2014 +6 days 🔍
05/27/2014 +1 days 🔍
09/17/2014 +113 days 🔍
06/19/2021 +2467 days 🔍

Sourcesinfo

Advisory: Bug 1097500
Researcher: Michael Nelson, Natalia Bidart, James Westby
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2014-1418 (🔍)
GCVE (CVE): GCVE-0-2014-1418
GCVE (VulDB): GCVE-100-13253

OVAL: 🔍

X-Force: 93179 - Django Vary and Cache-Control headers information disclosure, Medium Risk
SecurityFocus: 67408 - Django 'Vary Header' Information Disclosure Vulnerability
Secunia: 61281 - SUSE update for python-django, Moderately Critical
OSVDB: 107011
Vulnerability Center: 44640 - Django Remote Information Disclosure via a Request From Certain Browsers, Medium

See also: 🔍

Entryinfo

Created: 05/20/2014 10:28
Updated: 06/19/2021 18:34
Changes: 05/20/2014 10:28 (85), 05/29/2017 08:48 (5), 06/19/2021 18:34 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!