PHP up to 5.2.0 zend_hash_init a:2147483649:{ 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.
4.8$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in PHP up to 5.2.0. The affected element is the function zend_hash_init. Performing a manipulation of the argument a:2147483649:{ results in memory corruption. This vulnerability is known as CVE-2007-0988. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in PHP up to 5.2.0 (Programming Language Software). This affects the function zend_hash_init. The manipulation of the argument a:2147483649:{ with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:

The zend_hash_init function in PHP 5 before 5.2.1 and PHP 4 before 4.4.5, when running on a 64-bit platform, allows context-dependent attackers to cause a denial of service (infinite loop) by unserializing certain integer expressions, which only cause 32-bit arguments to be used after the check for a negative value, as demonstrated by an "a:2147483649:{" argument.

The bug was discovered 02/08/2007. The weakness was published 02/09/2007 (Website). The advisory is shared at php.net. This vulnerability is uniquely identified as CVE-2007-0988 since 02/16/2007. It is possible to initiate the attack remotely. No form of authentication is needed for 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 29378 (SuSE 10 Security Update : PHP5 (ZYPP Patch Number 3290)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 12259 (PHP Prior to 5.2.1/4.4.5 Multiple Vulnerabilities).

Upgrading to version 5.2.1 eliminates this vulnerability. A possible mitigation has been published 4 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (32709), Tenable (29378), OSVDB (32762†), Secunia (SA24089†) and SecurityTracker (ID 1017671†). Similar entries are available at VDB-2920, VDB-2911, VDB-2914 and VDB-2917. 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: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: 29378
Nessus Name: SuSE 10 Security Update : PHP5 (ZYPP Patch Number 3290)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 58119
OpenVAS Name: Debian Security Advisory DSA 1264-1 (php4)
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: PHP 5.2.1

Timelineinfo

02/08/2007 🔍
02/09/2007 +1 days 🔍
02/09/2007 +0 days 🔍
02/09/2007 +0 days 🔍
02/16/2007 +6 days 🔍
02/20/2007 +4 days 🔍
02/20/2007 +0 days 🔍
02/20/2007 +0 days 🔍
02/26/2007 +6 days 🔍
05/08/2007 +71 days 🔍
12/13/2007 +219 days 🔍
03/13/2015 +2647 days 🔍
07/15/2019 +1585 days 🔍

Sourcesinfo

Product: php.org

Advisory: php.net
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2007-0988 (🔍)
GCVE (CVE): GCVE-0-2007-0988
GCVE (VulDB): GCVE-100-35085

OVAL: 🔍

X-Force: 32709
Secunia: 24089 - PHP Multiple Vulnerabilities, Moderately Critical
OSVDB: 32762 - PHP on 64-bit zend_hash_init Function Remote DoS
SecurityTracker: 1017671
Vulnerability Center: 14381 - PHP zend_hash_init Function Denial of Service, Medium
Vupen: ADV-2007-1991

See also: 🔍

Entryinfo

Created: 03/13/2015 12:16
Updated: 07/15/2019 11:36
Changes: 03/13/2015 12:16 (88), 07/15/2019 11:36 (2)
Complete: 🔍
Cache ID: 216:743: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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!