# CVE-2011-10021: Magix Musik Maker <= v16 .mmm Stack-Based Buffer Overflow

> Attackers can execute arbitrary code by tricking users into opening a malicious .mmm file in Magix Musik Maker.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** No
- **Published:** 20 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-x945-8rv2-29j8

## What is CVE-2011-10021?

CVE-2011-10021 is a high-severity memory corruption vulnerability in Magix Musik Maker, published on 20 Aug 2025. 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

Magix Musik Maker 16 is vulnerable to a stack-based buffer overflow due to improper handling of .mmm arrangement files. The vulnerability arises from an unsafe strcpy() operation that fails to validate input length, allowing attackers to overwrite the Structured Exception Handler (SEH). By crafting a malicious .mmm file, an attacker can trigger the overflow when the file is opened, potentially leading to arbitrary code execution. This vulnerability was remediated in version 17.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2011-10021 being exploited?

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

Public exploit code:

- Magix Musik Maker 16 .mmm Stack Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-10021 is a high-severity memory corruption vulnerability in Magix Musik Maker, published on 20 Aug 2025. 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-2011-10021 exists.

Affected product: Magix Musik Maker. 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-10021/ (Markdown: https://insights.sbomify.com/CVE-2011-10021/index.md)
```

## Sources

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

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