# CVE-2011-0501: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a malicious .mamx file in Music Animation Machine MIDI Player.

- **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:** No
- **Published:** 20 Jan 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xgrf-pj3c-wvq6

## What is CVE-2011-0501?

CVE-2011-0501 is a critical memory corruption vulnerability in n/a, published on 20 Jan 2011. 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

Stack-based buffer overflow in Music Animation Machine MIDI Player 2006aug19 Release 035 and possibly other versions allows user-assisted remote attackers to execute arbitrary code via a long line in a .mamx file.

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

## Which versions are affected by CVE-2011-0501?

It affects 1 product.


Products: Musanim Music Animation Machine Midi Player.

## How do I fix CVE-2011-0501?

No fix has been published for CVE-2011-0501 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-0501 being exploited?

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

Public exploit code:

- Music Animation Machine MIDI Player - Local Buffer Overflow (SEH) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-0502](https://insights.sbomify.com/CVE-2011-0502/): Denial of service in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0501 and fix it if it is affected.

What it is: CVE-2011-0501 is a critical memory corruption vulnerability in n/a, published on 20 Jan 2011. An attacker can exploit it over the internet without logging in, 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-2011-0501 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-2011-0501/ (Markdown: https://insights.sbomify.com/CVE-2011-0501/index.md)
```

## Sources

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

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