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

> Buffer overflows in mpg123 allow attackers to cause a crash or potentially execute code via a malicious MP3 file.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/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:** 6 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1655, DSA-1074-1, GHSA-4wcr-9qqc-2rr4

## What is CVE-2006-1655?

CVE-2006-1655 is a medium-severity memory corruption vulnerability in n/a, published on 6 Apr 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

Multiple buffer overflows in mpg123 0.59r allow user-assisted attackers to trigger a segmentation fault and possibly have other impacts via a certain MP3 file, as demonstrated by mpg1DoS3.  NOTE: this issue might be related to CVE-2004-0991, but it is not clear.

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

It affects 1 product.


Products: Mpg123 Mpg123.

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

Upgrade to a fixed version.

## Is CVE-2006-1655 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1301](https://insights.sbomify.com/CVE-2009-1301/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-1284](https://insights.sbomify.com/CVE-2004-1284/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0982](https://insights.sbomify.com/CVE-2004-0982/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-12839](https://insights.sbomify.com/CVE-2017-12839/): Memory corruption in n/a (high 8.3)
- [CVE-2014-9497](https://insights.sbomify.com/CVE-2014-9497/): Buffer overflow in mpg123 before 1.18.0. (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1655 is a medium-severity memory corruption vulnerability in n/a, published on 6 Apr 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: There is no known exploitation of CVE-2006-1655 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-2006-1655/ (Markdown: https://insights.sbomify.com/CVE-2006-1655/index.md)
```

## Sources

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

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