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-2014-4049

php: heap-based buffer overflow in DNS TXT record parsing

Overview

Published
18 Jun 2014
Modified
6 May 2026
Medium CVE
0 Registry packages
236 OS packages
3 Linux distributions
Yes Fix available

Description

Heap-based buffer overflow in the php_parserr function in ext/standard/dns.c in PHP 5.6.0beta4 and earlier allows remote servers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted DNS TXT record, related to the dns_get_record function.

Source: OX vulnerability database

Severity

5.1 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
High
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

Weakness: CWE-119

Affected packages · 0

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

Operating systems · 7 fixes

Oracle Linux 1 release · 1 package

fixed 1
php
Oracle Linux fixes for CVE-2014-4049
ReleasePackageFixed in
7 php +24 5.4.16-23.el7_0

Red Hat 1 release · 3 packages

fixed 3
php54-php php php55-php
Red Hat fixes for CVE-2014-4049
ReleasePackageFixed inAdvisory
7 php54-php +22 0:5.4.16-22.el7 RHSA-2014:1765
7 php +24 0:5.4.16-23.el7_0 RHSA-2014:1013
7 php55-php +24 0:5.5.6-13.el7 RHSA-2014:1766

openSUSE 1 release · 3 packages

fixed 3
apache2-mod-php5 apache2-mod-php7 php8
openSUSE fixes for CVE-2014-4049
ReleasePackageFixed inAdvisory
Tumbleweed apache2-mod-php5 +58 5.6.28-1.1 openSUSE-SU-2024:10344-1
Tumbleweed apache2-mod-php7 +56 7.0.14-1.4 openSUSE-SU-2024:10290-1
Tumbleweed php8 +46 8.0.11-1.1 openSUSE-SU-2024:11169-1

References

Show all 31 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.