# CVE-2017-9053: Memory corruption in n/a

> A heap-based buffer over-read in libdwarf allows attackers to cause denial of service or disclose sensitive memory contents via crafted DWARF data.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-9053, GHSA-m3rv-r3jp-6fhp, UBUNTU-CVE-2017-9053

## What is CVE-2017-9053?

CVE-2017-9053 is a critical memory corruption vulnerability in n/a, published on 18 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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).

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2017-9053?

It affects 1 product.


Products: Libdwarf Project Libdwarf.

## How do I fix CVE-2017-9053?

Apply the vendor's patch.

## Is CVE-2017-9053 being exploited?

There is no known exploitation of CVE-2017-9053 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-9052](https://insights.sbomify.com/CVE-2017-9052/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9054](https://insights.sbomify.com/CVE-2017-9054/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-9055](https://insights.sbomify.com/CVE-2017-9055/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-9558](https://insights.sbomify.com/CVE-2016-9558/): Integer overflow in n/a (critical 9.8)
- [CVE-2016-9480](https://insights.sbomify.com/CVE-2016-9480/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9053 and fix it if it is affected.

What it is: CVE-2017-9053 is a critical memory corruption vulnerability in n/a, published on 18 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9053 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9053/ (Markdown: https://insights.sbomify.com/CVE-2017-9053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9053
- OSV: https://osv.dev/vulnerability/CVE-2017-9053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9053/
Summaries are generated and may contain mistakes; the official description above is the record.