Django 0.95 privilege escalation

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

Summaryinfo

A vulnerability, which was classified as critical, has been found in Django 0.95. This affects an unknown part. The manipulation leads to privilege escalation. This vulnerability is listed as CVE-2007-0405. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Django 0.95 (Content Management System). This issue affects an unknown functionality. The manipulation with an unknown input leads to a privilege escalation vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

The LazyUser class in the AuthenticationMiddleware for Django 0.95 does not properly cache the user name across requests, which allows remote authenticated users to gain the privileges of a different user.

The weakness was presented 01/22/2007 (Website). The advisory is shared at secunia.com. The identification of this vulnerability is CVE-2007-0405 since 01/22/2007. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (31628), SecurityFocus (BID 22138†) and Secunia (SA23826†). See VDB-34552 for similar entry. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.3

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/18/2007 🔍
01/19/2007 +0 days 🔍
01/22/2007 +3 days 🔍
01/22/2007 +0 days 🔍
01/22/2007 +0 days 🔍
03/13/2015 +2972 days 🔍
08/17/2018 +1253 days 🔍

Sourcesinfo

Advisory: secunia.com⛔
Status: Not defined
Confirmation: 🔍

CVE: CVE-2007-0405 (🔍)
GCVE (CVE): GCVE-0-2007-0405
GCVE (VulDB): GCVE-100-34553
X-Force: 31628
SecurityFocus: 22138 - Django Authentication Bypass Weakness
Secunia: 23826 - Django Two Vulnerabilities, Moderately Critical

See also: 🔍

Entryinfo

Created: 03/13/2015 10:40
Updated: 08/17/2018 07:19
Changes: 03/13/2015 10:40 (47), 08/17/2018 07:19 (7)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!