# CVE-2024-53589: Memory corruption in n/a

> A buffer overflow in GNU objdump's BFD library allows attackers to execute arbitrary code or cause denial of service via malicious tekhex files.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2024
- **Updated:** 14 Mar 2025
- **Also known as:** BELL-CVE-2024-53589, DEBIAN-CVE-2024-53589, ECHO-7c8e-b9e2-9d54, GHSA-6hcg-vqw2-35jw, ROOT-OS-DEBIAN-12-CVE-2024-53589

## What is CVE-2024-53589?

CVE-2024-53589 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

GNU objdump 2.43 is vulnerable to Buffer Overflow in the BFD (Binary File Descriptor) library's handling of tekhex format files.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-53589?


## How do I fix CVE-2024-53589?

Upgrade to a fixed version.

## Is CVE-2024-53589 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53589 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53589 and fix it if it is affected.

What it is: CVE-2024-53589 is a high-severity memory corruption vulnerability in n/a, published on 5 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53589 exists.

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-2024-53589/ (Markdown: https://insights.sbomify.com/CVE-2024-53589/index.md)
```

## Sources

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

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