Python Software Foundation up to 2.4.2 realpath stack-based overflow

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

Summaryinfo

A vulnerability marked as problematic has been reported in Python Software Foundation Python up to 2.4.2. Affected by this vulnerability is the function realpath. This manipulation causes stack-based overflow. This vulnerability is registered as CVE-2006-1542. Furthermore, an exploit is available.

Detailsinfo

A vulnerability has been found in Python Software Foundation Python up to 2.4.2 (Programming Language Software) and classified as problematic. Affected by this vulnerability is the function realpath. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Stack-based buffer overflow in Python 2.4.2 and earlier, running on Linux 2.6.12.5 under gcc 4.0.3 with libc 2.3.5, allows local users to cause a "stack overflow," and possibly gain privileges, by running a script from a current working directory that has a long name, related to the realpath function. NOTE: this might not be a vulnerability. However, the fact that it appears in a programming language interpreter could mean that some applications are affected, although attack scenarios might be limited because the attacker might already need to cross privilege boundaries to cause an exploitable program to be placed in a directory with a long name; or, depending on the method that Python uses to determine the current working directory, setuid applications might be affected.

The weakness was published 03/19/2006 by Gotfault Security (Website). The advisory is shared at redhat.com. This vulnerability is known as CVE-2006-1542. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

A public exploit has been developed by Gotfault Security and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 43836 (RHEL 4 : Solaris client in Satellite Server (RHSA-2008:0264)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks.

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 (25664), Exploit-DB (1591), Tenable (43836), OSVDB (24042†) and Secunia (SA31492†). Similar entry is available at VDB-1643. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.6

VulDB Base Score: 5.9
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Gotfault Security
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 43836
Nessus Name: RHEL 4 : Solaris client in Satellite Server (RHSA-2008:0264)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/22/2006 🔍
03/18/2006 +24 days 🔍
03/18/2006 +0 days 🔍
03/19/2006 +1 days 🔍
03/22/2006 +3 days 🔍
03/30/2006 +7 days 🔍
03/30/2006 +0 days 🔍
11/17/2010 +1693 days 🔍
03/12/2015 +1576 days 🔍
06/18/2024 +3386 days 🔍

Sourcesinfo

Advisory: redhat.com
Researcher: Gotfault Security
Status: Confirmed

CVE: CVE-2006-1542 (🔍)
GCVE (CVE): GCVE-0-2006-1542
GCVE (VulDB): GCVE-100-29425
X-Force: 25664
Secunia: 31492
OSVDB: 24042 - Python Interpreter realpath() Function Overflow
Vulnerability Center: 28261 - Python 2.4.2 and Earlier on Linux 2.6.12.5 Local Stack-Based Buffer Overflow Vulnerability, Medium

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

Entryinfo

Created: 03/12/2015 12:19
Updated: 06/18/2024 19:23
Changes: 03/12/2015 12:19 (56), 03/09/2017 11:49 (15), 07/08/2021 14:27 (3), 07/08/2021 14:29 (1), 06/18/2024 19:23 (16)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!