Django 1.8.2 Session request.session resource management

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 described as problematic has been identified in Django 1.8.2. Affected by this issue is some unknown functionality of the component Session Handler. Executing a manipulation of the argument request.session can lead to resource management. This vulnerability is handled as CVE-2015-5143. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability has been found in Django 1.8.2 (Content Management System) and classified as problematic. This vulnerability affects an unknown code block of the component Session Handler. The manipulation of the argument request.session with an unknown input leads to a resource management vulnerability. The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect availability. CVE summarizes:

The session backends in Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (session store consumption) via multiple requests with unique session keys.

The weakness was released 07/08/2015 by Eric Peterson and Lin Hua Cheng as Security releases issued: 1.8.3, 1.7.9, 1.4.21 as confirmed news (Website). The advisory is shared for download at djangoproject.com. The public release was coordinated with the vendor. This vulnerability was named CVE-2015-5143 since 06/29/2015. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The advisory points out:

In previous versions of Django, the session backends created a new empty record in the session storage anytime request.session was accessed and there was a session key provided in the request cookies that didn't already have a session record. This could allow an attacker to easily create many new session records simply by sending repeated requests with unknown session keys, potentially filling up the session store or causing other users' session records to be evicted.

The vulnerability scanner Nessus provides a plugin with the ID 84626 (Debian DSA-3305-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 124352 (Fedora Security Update for python-django (FEDORA-2015-1)).

Upgrading to version 1.8.3 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The news contains the following remark:

The built-in session backends now create a session record only if the session is actually modified; empty session records are not created. Thus this potential DoS is now only possible if the site chooses to expose a session-modifying view to anonymous users. As each built-in session backend was fixed separately (rather than a fix in the core sessions framework), maintainers of third-party session backends should check whether the same vulnerability is present in their backend and correct it if so.

The vulnerability is also documented in the databases at Tenable (84626), SecurityFocus (BID 75666†), SecurityTracker (ID 1032820†) and Vulnerability Center (SBV-51612†). Entries connected to this vulnerability are available at VDB-76397, VDB-76398, VDB-77329 and VDB-77330. Once again VulDB remains the best source for vulnerability data.

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: Resource management
CWE: CWE-399 / CWE-404
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: 84626
Nessus Name: Debian DSA-3305-1 : python-django - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 703305
OpenVAS Name: Debian Security Advisory DSA 3305-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.8.3

Timelineinfo

06/29/2015 🔍
07/08/2015 +9 days 🔍
07/08/2015 +0 days 🔍
07/08/2015 +0 days 🔍
07/08/2015 +0 days 🔍
07/09/2015 +1 days 🔍
07/10/2015 +1 days 🔍
07/14/2015 +4 days 🔍
07/28/2015 +14 days 🔍
05/24/2022 +2492 days 🔍

Sourcesinfo

Advisory: Security releases issued: 1.8.3, 1.7.9, 1.4.21
Researcher: Eric Peterson, Lin Hua Cheng
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2015-5143 (🔍)
GCVE (CVE): GCVE-0-2015-5143
GCVE (VulDB): GCVE-100-76396

OVAL: 🔍

SecurityFocus: 75666 - Django CVE-2015-5143 Denial of Service Vulnerability
SecurityTracker: 1032820 - Django Bugs Let Remote Users Deny Service and Conduct HTTP/Header Response Splitting Attacks
Vulnerability Center: 51612 - Django <1.4.21, 1.5 - 1.7.8, 1.8 - 1.8.2 Remote DoS via Session Store, High

See also: 🔍

Entryinfo

Created: 07/10/2015 10:38
Updated: 05/24/2022 06:35
Changes: 07/10/2015 10:38 (73), 08/03/2017 03:20 (11), 05/24/2022 06:35 (3)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

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!