Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-4598

php: missing null byte checks for paths in DOM and GD extensions

Overview

Published
16 May 2016
Modified
6 May 2026
Medium CVE
0 Registry packages
100 OS packages
2 Linux distributions
Yes Fix available

Description

PHP before 5.4.42, 5.5.x before 5.5.26, and 5.6.x before 5.6.10 does not ensure that pathnames lack %00 sequences, which might allow remote attackers to read or write to arbitrary files via crafted input to an application that calls (1) a DOMDocument save method or (2) the GD imagepsloadfont function, as demonstrated by a filename\0.html attack that bypasses an intended configuration in which client users may write to only .html files.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Weakness: CWE-20

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 7 fixes

Oracle Linux 1 release · 3 packages

fixed 3
php php54-php php55-php
Oracle Linux fixes for CVE-2015-4598
ReleasePackageFixed in
7 php +24 5.4.16-36.el7_1
7 php54-php +22 5.4.40-3.el7
7 php55-php +24 5.5.21-4.el7

Red Hat 1 release · 4 packages

fixed 4
php php54-php php55-php rh-php56-php
Red Hat fixes for CVE-2015-4598
ReleasePackageFixed inAdvisory
7 php +24 0:5.4.16-36.el7_1 RHSA-2015:1135
7 php54-php +22 0:5.4.40-3.el7 RHSA-2015:1219
7 php55-php +24 0:5.5.21-4.el7 RHSA-2015:1186
7 rh-php56-php +26 0:5.6.5-7.el7 RHSA-2015:1187

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.