PHP 5.1/5.1.0/5.1.1/5.1.2/5.1.4 safe_mode/open_basedir memory corruption

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

Summaryinfo

A vulnerability has been found in PHP 5.1/5.1.0/5.1.1/5.1.2/5.1.4 and classified as problematic. This vulnerability affects unknown code. This manipulation of the argument safe_mode/open_basedir causes memory corruption. This vulnerability is tracked as CVE-2006-4481. Moreover, an exploit is present. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical was found in PHP 5.1/5.1.0/5.1.1/5.1.2/5.1.4 (Programming Language Software). Affected by this vulnerability is an unknown part. The manipulation of the argument safe_mode/open_basedir with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The (1) file_exists and (2) imap_reopen functions in PHP before 5.1.5 do not check for the safe_mode and open_basedir settings, which allows local users to bypass the settings. NOTE: the error_log function is covered by CVE-2006-3011, and the imap_open function is covered by CVE-2006-1017.

The weakness was disclosed 08/18/2006 with PHP Team (Website). It is possible to read the advisory at php.net. This vulnerability is known as CVE-2006-4481 since 08/31/2006. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.

It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 22343 (FreeBSD : php -- multiple vulnerabilities (ea09c5df-4362-11db-81e1-000e0c2e438a)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165127 (SUSE Security Update for php4, php5 (SUSE-SA:2006:052)).

Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at php.net. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published 4 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (22343), SecurityFocus (BID 19582†) and Secunia (SA21546†). The entries VDB-2269, VDB-2469, VDB-2468 and VDB-2466 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: 10.0
VulDB Meta Temp Score: 9.0

VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 22343
Nessus Name: FreeBSD : php -- multiple vulnerabilities (ea09c5df-4362-11db-81e1-000e0c2e438a)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 57375
OpenVAS Name: FreeBSD Ports: php4, php5
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: 🔍

Patch: php.net

Timelineinfo

08/18/2006 🔍
08/18/2006 +0 days 🔍
08/18/2006 +0 days 🔍
08/31/2006 +13 days 🔍
08/31/2006 +0 days 🔍
09/13/2006 +13 days 🔍
09/14/2006 +1 days 🔍
04/24/2019 +4605 days 🔍

Sourcesinfo

Product: php.org

Advisory: php.net
Researcher: http://www.php.net
Organization: PHP Team
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-4481 (🔍)
GCVE (CVE): GCVE-0-2006-4481
GCVE (VulDB): GCVE-100-2467
SecurityFocus: 19582 - PHP Multiple Input Validation Vulnerabilities
Secunia: 21546 - PHP Multiple Vulnerabilities, Highly Critical
Vupen: ADV-2006-3318

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

Entryinfo

Created: 08/18/2006 16:22
Updated: 04/24/2019 10:36
Changes: 08/18/2006 16:22 (85), 04/24/2019 10:36 (2)
Complete: 🔍
Cache ID: 216:BDD: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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!