What is the CVSS score of CVE-2014-4049?

CVE-2014-4049 has a CVSS 2.0 base score of 5.1 (Medium). CVSS vector: AV:N/AC:H/Au:N/C:P/I:P/A:P. EPSS exploitation probability: 30.7%.

Is there a patch available for CVE-2014-4049?

Yes, a patch is available for CVE-2014-4049. Update the affected software to the latest version immediately.

PHP CVE-2014-4049

MEDIUM

Buffer Overflow (CWE-119)

2014-06-18 cve@mitre.org

Denial Of Service RCE PHP Buffer Overflow Opensuse Debian Linux

5.1

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.1 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 18, 2014 - 19:55 cve.org

MEDIUM 5.1

DescriptionCVE.org

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.

AnalysisAI

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. Rated medium severity (CVSS 5.1), this vulnerability is remotely exploitable. Epss exploitation probability 30.7%.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. 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. Affected products include: Opensuse, Php, Debian Debian Linux.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.