What is the CVSS score of CVE-2016-5038?

CVE-2016-5038 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 1.4%.

Is there a public PoC exploit available for CVE-2016-5038?

Yes, a public proof-of-concept exploit is available for CVE-2016-5038. Prioritise patching immediately. EPSS: 1.4%.

Is there a patch available for CVE-2016-5038?

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

Libdwarf CVE-2016-5038

HIGH

Out-of-bounds Read (CWE-125)

2017-02-17 cve@mitre.org

Buffer Overflow Denial Of Service Information Disclosure Libdwarf

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Feb 17, 2017 - 17:59 cve.org

HIGH 7.5

DescriptionCVE.org

AnalysisAI

The dwarf_get_macro_startend_file function in dwarf_macro5.c in libdwarf before 20160923 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted string offset for. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Read (CWE-125), which allows attackers to read data from memory outside the intended buffer boundaries. The dwarf_get_macro_startend_file function in dwarf_macro5.c in libdwarf before 20160923 allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted string offset for .debug_str. Affected products include: Libdwarf Project Libdwarf. Version information: before 20160923.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate array indices and buffer lengths. Use memory-safe languages. Enable AddressSanitizer during testing.