# CVE-2011-10024: MJM Core Player 2011 .s3m File Stack-Based Buffer Overflow

> Attacker can execute arbitrary code by tricking a user into opening a malicious .s3m file in MJM Core Player.

- **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:** 7 Apr 2026
- **Also known as:** GHSA-qrg8-4g95-jxg4

## What is CVE-2011-10024?

CVE-2011-10024 is a high-severity memory corruption vulnerability in MJM Software Core Player, 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

MJM Core Player (likely now referred to as MJM Player) 2011 is vulnerable to a stack-based buffer overflow when parsing specially crafted .s3m music files. The vulnerability arises from improper bounds checking in the file parser, allowing an attacker to overwrite memory on the stack and execute arbitrary code. Exploitation is triggered when a user opens a malicious .s3m file, and the exploit bypasses DEP and ASLR protections using a ROP chain.

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

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


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

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

## Is CVE-2011-10024 being exploited?

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

Public exploit code:

- MJM Core Player 2011 .s3m Stack Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-10024 is a high-severity memory corruption vulnerability in MJM Software Core Player, 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-10024 exists.

Affected product: MJM Software Core Player. 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-10024/ (Markdown: https://insights.sbomify.com/CVE-2011-10024/index.md)
```

## Sources

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

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