# CVE-2005-0020: Memory corruption in n/a

> Local attackers can execute arbitrary code via a buffer overflow in the playmidi utility, requiring local access to the system.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jan 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0020, DSA-641-1, GHSA-9wjx-vxh5-8xrx

## What is CVE-2005-0020?

CVE-2005-0020 is a high-severity memory corruption vulnerability in Mandrakesoft Mandrake Linux, published on 22 Jan 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in playmidi before 2.4 allows local users to execute arbitrary code.

## Which versions are affected by CVE-2005-0020?

It affects 3 products.


Products: Mandrakesoft Mandrake Linux, Mandrakesoft Mandrake Linux Corporate Server, Playmidi Playmidi.

## How do I fix CVE-2005-0020?

Upgrade to a fixed version.

## Is CVE-2005-0020 being exploited?

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

## Other vulnerabilities in Mandrakesoft Mandrake Linux

- [CVE-2004-1187](https://insights.sbomify.com/CVE-2004-1187/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1188](https://insights.sbomify.com/CVE-2004-1188/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0041](https://insights.sbomify.com/CVE-2003-0041/): Command injection in n/a (critical 10.0)
- [CVE-2000-1042](https://insights.sbomify.com/CVE-2000-1042/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1043](https://insights.sbomify.com/CVE-2000-1043/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0020 and fix it if it is affected.

What it is: CVE-2005-0020 is a high-severity memory corruption vulnerability in Mandrakesoft Mandrake Linux, published on 22 Jan 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0020 in the wild and no public exploit code.

Affected product: Mandrakesoft Mandrake Linux. 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-2005-0020/ (Markdown: https://insights.sbomify.com/CVE-2005-0020/index.md)
```

## Sources

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

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