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

> Attackers can execute arbitrary code by tricking users into opening malicious ABC music files with the abc2ps converter.

- **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:** 25 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1041-1, GHSA-gxx2-vmf7-f9v6

## What is CVE-2006-1513?

CVE-2006-1513 is a medium-severity memory corruption vulnerability in n/a, published on 25 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 abc2ps before 1.3.3 allow user-assisted attackers to execute arbitrary code via crafted ABC music files.

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

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

It affects 1 product.


Products: Abc2ps Abc2ps.

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

Upgrade to a fixed version.

## Is CVE-2006-1513 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1278](https://insights.sbomify.com/CVE-2004-1278/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1513 is a medium-severity memory corruption vulnerability in n/a, published on 25 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-1513 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-1513/ (Markdown: https://insights.sbomify.com/CVE-2006-1513/index.md)
```

## Sources

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

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