# CVE-2010-2971: Memory corruption in n/a

> Remote attackers can trigger a buffer over-read and potential code execution via a crafted Impulse Tracker file in libmikmod.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 4 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-2971, GHSA-7xx4-x85v-pc9j

## What is CVE-2010-2971?

CVE-2010-2971 is a critical memory corruption vulnerability in n/a, published on 4 Aug 2010. 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

loaders/load_it.c in libmikmod, possibly 3.1.12, does not properly account for the larger size of name##env relative to name##tick and name##node, which allows remote attackers to trigger a buffer over-read and possibly have unspecified other impact via a crafted Impulse Tracker file, a related issue to CVE-2010-2546.  NOTE: this issue exists because of an incomplete fix for CVE-2009-3995.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-2971?

It affects 1 product.


Products: Raphael Assenat Libmikmod.

## How do I fix CVE-2010-2971?

Upgrade to a fixed version.

## Is CVE-2010-2971 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2546](https://insights.sbomify.com/CVE-2010-2546/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2971 and fix it if it is affected.

What it is: CVE-2010-2971 is a critical memory corruption vulnerability in n/a, published on 4 Aug 2010. 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-2010-2971 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-2010-2971/ (Markdown: https://insights.sbomify.com/CVE-2010-2971/index.md)
```

## Sources

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

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