# CVE-2025-1147: GNU Binutils nm nm.c internal_strlen buffer overflow

> A buffer overflow in GNU Binutils nm allows remote attackers to potentially execute code or cause denial of service via crafted input.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Feb 2025
- **Updated:** 4 Apr 2025
- **Also known as:** AZL-56603, AZL-56640, BELL-CVE-2025-1147, DEBIAN-CVE-2025-1147, ECHO-26e5-773a-f5f8, GHSA-73x9-xqqp-w963, ROOT-OS-DEBIAN-12-CVE-2025-1147, UBUNTU-CVE-2025-1147

## What is CVE-2025-1147?

CVE-2025-1147 is a low-severity memory corruption vulnerability in Gnu Binutils, published on 10 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-1147?

It affects 1 product.


Products: Gnu Binutils.

## How do I fix CVE-2025-1147?

Upgrade to a fixed version.

## Is CVE-2025-1147 being exploited?

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

## Other vulnerabilities in Gnu Binutils

- [CVE-2017-7614](https://insights.sbomify.com/CVE-2017-7614/): Null dereference in n/a (critical 9.8)
- [CVE-2014-9939](https://insights.sbomify.com/CVE-2014-9939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7226](https://insights.sbomify.com/CVE-2017-7226/): Information disclosure in n/a (critical 9.1)
- [CVE-2017-6969](https://insights.sbomify.com/CVE-2017-6969/): Information disclosure in n/a (critical 9.1)
- [CVE-2020-19726](https://insights.sbomify.com/CVE-2020-19726/): Denial of service in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1147 and fix it if it is affected.

What it is: CVE-2025-1147 is a low-severity memory corruption vulnerability in Gnu Binutils, published on 10 Feb 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1147 in the wild and no public exploit code.

Affected product: Gnu Binutils. 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-2025-1147/ (Markdown: https://insights.sbomify.com/CVE-2025-1147/index.md)
```

## Sources

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

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