How severe is CVE-2017-9053?

CVE-2017-9053 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.

Is CVE-2017-9053 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-9053?

CVE-2017-9053 affects Libdwarf Project Libdwarf. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-9053?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2017-9053 published?

CVE-2017-9053 was published on 2017-05-18 and last updated on 2026-06-17.

CVE-2017-9053

CVE-2017-9053 is a critical-severity vulnerability in Libdwarf Project Libdwarf with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-125.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
CVSS v2: 6.4
EPSS exploit prediction: 2% (75th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-125
Affected product: Libdwarf Project Libdwarf
Published: 2017-05-18
Last modified: 2026-06-17

Description

An issue, also known as DW201703-005, was discovered in libdwarf 2017-03-21. A heap-based buffer over-read in _dwarf_read_loc_expr_op() is due to a failure to check a pointer for being in bounds (in a few places in this function).

Frequently asked questions

What is CVE-2017-9053?: An issue, also known as DW201703-005, was discovered in libdwarf 2017-03-21. A heap-based buffer over-read in _dwarf_read_loc_expr_op() is due to a failure to check a pointer for being in bounds (in a few places in this function).
How severe is CVE-2017-9053?: CVE-2017-9053 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.
Is CVE-2017-9053 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (75th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-9053?: CVE-2017-9053 affects Libdwarf Project Libdwarf. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-9053?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-9053 published?: CVE-2017-9053 was published on 2017-05-18 and last updated on 2026-06-17.

References

https://www.prevanders.net/dwarfbug.html

Affected products (1)

cpe:2.3:a:libdwarf_project:libdwarf:2017-03-21:*:*:*:*:*:*:*

More vulnerabilities in Libdwarf Project Libdwarf

CVE-2017-9055 — Critical (CVSS 9.8): An issue, also known as DW201703-001, was discovered in libdwarf 2017-03-21. In dwarf_formsdata() a few data types were…
CVE-2017-9054 — Critical (CVSS 9.8): An issue, also known as DW201703-002, was discovered in libdwarf 2017-03-21. In _dwarf_decode_s_leb128_chk() a byte…
CVE-2017-9052 — Critical (CVSS 9.8): An issue, also known as DW201703-006, was discovered in libdwarf 2017-03-21. A heap-based buffer over-read in…
CVE-2016-9558 — Critical (CVSS 9.8): (1) libdwarf/dwarf_leb.c and (2) dwarfdump/print_frames.c in libdwarf before 20161124 allow remote attackers to have…
CVE-2016-9480 — Critical (CVSS 9.1): libdwarf 2016-10-21 allows context-dependent attackers to obtain sensitive information or cause a denial of service by…
CVE-2022-39170 — High (CVSS 8.8): libdwarf 0.4.1 has a double free in _dwarf_exec_frame_instr in dwarf_frame.c.

All CVEs affecting Libdwarf Project Libdwarf →

Other CWE-125 (Out-of-bounds Read) vulnerabilities

CVE-2026-24826 — Critical (CVSS 10.0): Out-of-bounds Write, Divide By Zero, NULL Pointer Dereference, Use of Uninitialized Resource, Out-of-bounds Read,…
CVE-2024-22004 — Critical (CVSS 10.0): Due to length check, an attacker with privilege access on a Linux Nonsecure operating system can trigger a…
CVE-2021-41556 — Critical (CVSS 10.0): sqclass.cpp in Squirrel through 2.2.5 and 3.x through 3.1 allows an out-of-bounds read (in the core interpreter) that…
CVE-2021-21777 — Critical (CVSS 10.0): An information disclosure vulnerability exists in the Ethernet/IP UDP handler functionality of EIP Stack Group OpENer…
CVE-2017-14451 — Critical (CVSS 10.0): An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. A…
CVE-2013-0767 — Critical (CVSS 10.0): The nsSVGPathElement::GetPathLengthScale function in Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and…

Browse all CWE-125 (Out-of-bounds Read) vulnerabilities →