PHP 4.4.4/5.2.0 Serialization deserialization

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

Summaryinfo

A vulnerability classified as critical has been found in PHP 4.4.4/5.2.0. This issue affects some unknown processing of the component Serialization. Performing a manipulation results in deserialization. This vulnerability was named CVE-2007-1701. In addition, an exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in PHP 4.4.4/5.2.0 (Programming Language Software). It has been classified as critical. This affects some unknown processing of the component Serialization. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

PHP 4 before 4.4.5, and PHP 5 before 5.2.1, when register_globals is enabled, allows context-dependent attackers to execute arbitrary code via deserialization of session data, which overwrites arbitrary global variables, as demonstrated by calling session_decode on a string beginning with "_SESSION|s:39:".

The bug was discovered 03/24/2007. The weakness was presented 03/26/2007 by Stefan Esser (Website). The advisory is shared at security.gentoo.org. This vulnerability is uniquely identified as CVE-2007-1701 since 03/26/2007. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.

The exploit is shared for download 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 24673 (CentOS 3 / 4 : php (CESA-2007:0076)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 156186 (Oracle Enterprise Linux Update for PHP (ELSA-2007:0076)).

Upgrading to version 4.4.5 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (33658), Exploit-DB (3572), Tenable (24673), SecurityFocus (BID 23120†) and OSVDB (33945†). See VDB-35532, VDB-35008, VDB-35007 and VDB-35006 for similar entries. 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: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Deserialization
CWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 24673
Nessus Name: CentOS 3 / 4 : php (CESA-2007:0076)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 100602
OpenVAS Name: PHP Session Data Deserialization Arbitrary Code Execution Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: PHP 4.4.5

Timelineinfo

02/19/2007 🔍
02/21/2007 +2 days 🔍
03/24/2007 +31 days 🔍
03/24/2007 +0 days 🔍
03/24/2007 +0 days 🔍
03/26/2007 +2 days 🔍
03/26/2007 +0 days 🔍
03/26/2007 +0 days 🔍
04/10/2007 +15 days 🔍
05/28/2007 +48 days 🔍
03/13/2015 +2846 days 🔍
01/02/2025 +3583 days 🔍

Sourcesinfo

Product: php.org

Advisory: security.gentoo.org
Researcher: Stefan Esser
Status: Confirmed

CVE: CVE-2007-1701 (🔍)
GCVE (CVE): GCVE-0-2007-1701
GCVE (VulDB): GCVE-100-35853

OVAL: 🔍

X-Force: 33658
SecurityFocus: 23120 - PHP Session Data Deserialization Arbitrary Code Execution Vulnerability
Secunia: 25445 - Gentoo update for php, Highly Critical
OSVDB: 33945 - CVE-2007-1701 - PHP - Code Execution Issue
Vulnerability Center: 14777 - PHP Code Execution via Deserializtion of Session Data, Low
Vupen: ADV-2007-1991

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

Entryinfo

Created: 03/13/2015 12:16
Updated: 01/02/2025 11:47
Changes: 03/13/2015 12:16 (81), 07/17/2019 12:41 (6), 01/02/2025 11:47 (19)
Complete: 🔍
Cache ID: 216::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 ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!