Django 1.8.1/1.8.2/1.8.6/1.9 Time Username 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.
2.9$0-$5k0.00

Summaryinfo

A vulnerability has been found in Django 1.8.1/1.8.2/1.8.6/1.9 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Time Handler. Performing a manipulation results in information disclosure (Username). This vulnerability is reported as CVE-2016-2513. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Django 1.8.1/1.8.2/1.8.6/1.9 (Content Management System). This affects an unknown part of the component Time Handler. The manipulation with an unknown input leads to a information disclosure vulnerability (Username). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

The password hasher in contrib/auth/hashers.py in Django before 1.8.10 and 1.9.x before 1.9.3 allows remote attackers to enumerate users via a timing attack involving login requests.

The weakness was disclosed 03/01/2016 by Sjoerd Job Postmus (Website). It is possible to read the advisory at djangoproject.com. This vulnerability is uniquely identified as CVE-2016-2513 since 02/19/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 89079 (Ubuntu 12.04 LTS / 14.04 LTS / 15.10 : python-django vulnerabilities (USN-2915-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Ubuntu Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 296002 (Solaris 11.3 Support Repository Update (SRU) 9.4.0 Missing).

Upgrading to version 1.8.10 or 1.9.3 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (111180), Tenable (89079), SecurityFocus (BID 83878†) and Vulnerability Center (SBV-58064†). The entries VDB-74783, VDB-78889, VDB-80607 and VDB-80673 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 2.9

VulDB Base Score: 3.1
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.1
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

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

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Unproven

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 89079
Nessus Name: Ubuntu 12.04 LTS / 14.04 LTS / 15.10 : python-django vulnerabilities (USN-2915-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for python-django FEDORA-2016-11183
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.10/1.9.3
Patch: github.com

Timelineinfo

02/19/2016 🔍
03/01/2016 +11 days 🔍
03/01/2016 +0 days 🔍
03/01/2016 +0 days 🔍
03/01/2016 +0 days 🔍
03/02/2016 +1 days 🔍
03/03/2016 +1 days 🔍
04/08/2016 +35 days 🔍
04/12/2016 +4 days 🔍
07/08/2022 +2278 days 🔍

Sourcesinfo

Product: github.com

Advisory: USN-2915-1
Researcher: Sjoerd Job Postmus
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-2513 (🔍)
GCVE (CVE): GCVE-0-2016-2513
GCVE (VulDB): GCVE-100-81147

OVAL: 🔍

X-Force: 111180 - Django time difference information disclosure
SecurityFocus: 83878 - Django CVE-2016-2513 Security Bypass Vulnerability
SecurityTracker: 1035152
Vulnerability Center: 58064 - Django <1.8.10 and 1.9 - 1.92 Password Hasher Remote Users Enumeration Vulnerability, Low

See also: 🔍

Entryinfo

Created: 03/03/2016 10:52
Updated: 07/08/2022 20:41
Changes: 03/03/2016 10:52 (76), 02/04/2019 11:35 (13), 07/08/2022 20:33 (5), 07/08/2022 20:41 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!