# CVE-2006-2465: Memory corruption in n/a

> Buffer overflow in MP3Info allows arbitrary code execution via long command line arguments, primarily posing a risk if the binary is setuid or setgid.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2465, GHSA-cm74-95vp-cwf5

## What is CVE-2006-2465?

CVE-2006-2465 is a medium-severity memory corruption vulnerability in n/a, published on 19 May 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in MP3Info 0.8.4 allows attackers to execute arbitrary code via a long command line argument.  NOTE: if mp3info is not installed setuid or setgid in any reasonable context, then this issue might not be a vulnerability.

## Which versions are affected by CVE-2006-2465?

It affects 1 product.


Products: Mp3info Mp3info.

## How do I fix CVE-2006-2465?

Upgrade to a fixed version.

## Is CVE-2006-2465 being exploited?

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

Public exploit code:

- MP3Info 0.8.5a - Buffer Overflow (exploitdb)
- MP3Info 0.8.5a - Local Buffer Overflow (SEH) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2465 and fix it if it is affected.

What it is: CVE-2006-2465 is a medium-severity memory corruption vulnerability in n/a, published on 19 May 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2465 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-2006-2465/ (Markdown: https://insights.sbomify.com/CVE-2006-2465/index.md)
```

## Sources

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

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