PHP up to 5.2.6 memnstr delimiter 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.
5.9$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in PHP up to 5.2.6. The affected element is the function memnstr. The manipulation of the argument delimiter leads to memory corruption. This vulnerability is traded as CVE-2008-3659. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in PHP up to 5.2.6 (Programming Language Software) and classified as critical. This issue affects the function memnstr. The manipulation of the argument delimiter with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity, and availability. The summary by CVE is:

Buffer overflow in the memnstr function in PHP 4.4.x before 4.4.9 and PHP 5.6 through 5.2.6 allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via the delimiter argument to the explode function. NOTE: the scope of this issue is limited since most applications would not use an attacker-controlled delimiter, but local attacks against safe_mode are feasible.

The bug was discovered 08/07/2008. The weakness was shared 08/07/2008 (Website). The advisory is shared at us-cert.gov. The identification of this vulnerability is CVE-2008-3659 since 08/12/2008. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

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 $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 34355 (Debian DSA-1647-1 : php5 - several vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 185076 (HP-UX Running Apache Web Server Suite Multiple Vulnerabilities (HPSBUX02431)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 3 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (44405), Tenable (34355), SecurityFocus (BID 30649†), OSVDB (47483†) and Secunia (SA31982†). The entries VDB-23858, VDB-30376, VDB-38768 and VDB-40710 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.5
VulDB Temp Score: 5.9
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: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 34355
Nessus Name: Debian DSA-1647-1 : php5 - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 61712
OpenVAS Name: Debian Security Advisory DSA 1647-1 (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: 🔍

Timelineinfo

08/07/2008 🔍
08/07/2008 +0 days 🔍
08/07/2008 +0 days 🔍
08/12/2008 +4 days 🔍
08/12/2008 +0 days 🔍
08/14/2008 +1 days 🔍
08/14/2008 +0 days 🔍
10/07/2008 +54 days 🔍
10/07/2008 +0 days 🔍
10/07/2008 +0 days 🔍
10/13/2008 +6 days 🔍
03/17/2015 +2346 days 🔍
08/01/2021 +2329 days 🔍

Sourcesinfo

Product: php.org

Advisory: us-cert.gov
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2008-3659 (🔍)
GCVE (CVE): GCVE-0-2008-3659
GCVE (VulDB): GCVE-100-43709

OVAL: 🔍

X-Force: 44405
SecurityFocus: 30649
Secunia: 31982
OSVDB: 47483 - PHP memnstr() Function Unspecified Overflow
SecurityTracker: 1020995
Vulnerability Center: 19700 - PHP 4.4-4.4.8, 5.2-5.2.6 memnstr Function Vulnerability Allows Remote DoS or Code Execution, High
Vupen: ADV-2008-2336

See also: 🔍

Entryinfo

Created: 03/17/2015 12:19
Updated: 08/01/2021 20:06
Changes: 03/17/2015 12:19 (74), 08/18/2019 09:48 (12), 08/01/2021 20:06 (4)
Complete: 🔍
Cache ID: 216:D03:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!