Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2006-5178


Race condition in the symlink function in PHP 5.1.6 and earlier allows local users to bypass the open_basedir restriction by using a combination of symlink, mkdir, and unlink functions to change the file path after the open_basedir check and before the file is opened by the underlying system, as demonstrated by symlinking a symlink into a subdirectory, to point to a parent directory via .. (dot dot) sequences, and then unlinking the resulting symlink.


Security Impact Summary

CVE-2006-5178 is a security vulnerability that . Impacting 1 product from php organizations running these solutions should prioritize assessment and patching.

Historical Context

Originally identified in 2006, this vulnerability predates many modern security frameworks and practices. The vulnerability landscape of that era was characterized by different threat models and less mature defense mechanisms compared to contemporary standards.


Published

2006-10-10T04:06:00.000

Last Modified

2025-04-09T00:30:58.490

Status

Deferred

Source

[email protected]

Severity

CVSSv2: 6.2 (MEDIUM)

CVSSv2 Vector

AV:L/AC:H/Au:N/C:C/I:C/A:C

  • Access Vector: LOCAL
  • Access Complexity: HIGH
  • Authentication: NONE
  • Confidentiality Impact: COMPLETE
  • Integrity Impact: COMPLETE
  • Availability Impact: COMPLETE
Exploitability Score

1.9

Impact Score

10.0

Weaknesses
  • Type: Primary
    CWE-362

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application php php ≤ 5.1.6 Yes
Application php php 4.0 Yes
Application php php 4.0.1 Yes
Application php php 4.0.1 Yes
Application php php 4.0.1 Yes
Application php php 4.0.2 Yes
Application php php 4.0.3 Yes
Application php php 4.0.4 Yes
Application php php 4.0.5 Yes
Application php php 4.0.6 Yes
Application php php 4.0.7 Yes
Application php php 4.0.7 Yes
Application php php 4.0.7 Yes
Application php php 4.0.7 Yes
Application php php 4.1.0 Yes
Application php php 4.1.1 Yes
Application php php 4.1.2 Yes
Application php php 4.2 Yes
Application php php 4.2.0 Yes
Application php php 4.2.1 Yes
Application php php 4.2.2 Yes
Application php php 4.2.3 Yes
Application php php 4.3.0 Yes
Application php php 4.3.1 Yes
Application php php 4.3.2 Yes
Application php php 4.3.3 Yes
Application php php 4.3.4 Yes
Application php php 4.3.5 Yes
Application php php 4.3.6 Yes
Application php php 4.3.7 Yes
Application php php 4.3.8 Yes
Application php php 4.3.9 Yes
Application php php 4.3.10 Yes
Application php php 4.3.11 Yes
Application php php 4.4.0 Yes
Application php php 4.4.1 Yes
Application php php 4.4.2 Yes
Application php php 4.4.3 Yes
Application php php 4.4.4 Yes
Application php php 5.0 Yes
Application php php 5.0 Yes
Application php php 5.0 Yes
Application php php 5.0.0 Yes
Application php php 5.0.1 Yes
Application php php 5.0.2 Yes
Application php php 5.0.3 Yes
Application php php 5.0.4 Yes
Application php php 5.0.5 Yes
Application php php 5.1.0 Yes
Application php php 5.1.1 Yes
Application php php 5.1.2 Yes
Application php php 5.1.3 Yes
Application php php 5.1.4 Yes
Application php php 5.1.5 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For php's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.