# CVE-2010-20111: Digital Music Pad <= 8.2.3.3.4 Stack Buffer Overflow

> A stack buffer overflow in Digital Music Pad allows arbitrary code execution when a malicious .pls file is opened.

- **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:** 21 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-gf45-cpf5-g5rx

## What is CVE-2010-20111?

CVE-2010-20111 is a high-severity memory corruption vulnerability in Digital Music Pad, published on 21 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

Digital Music Pad v8.2.3.3.4 contains a stack-based buffer overflow vulnerability in its playlist file parser. When opening a .pls file containing an excessively long string in the File1 field, the application fails to properly validate input length, resulting in corruption of the Structured Exception Handler (SEH) on the stack. This flaw may allow an attacker to control execution flow when the file is opened, potentially leading to arbitrary code execution.

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

## Which versions are affected by CVE-2010-20111?


## How do I fix CVE-2010-20111?

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

## Is CVE-2010-20111 being exploited?

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

Public exploit code:

- Digital Music Pad Version 8.2.3.3.4 Stack Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-20111 and fix it if it is affected.

What it is: CVE-2010-20111 is a high-severity memory corruption vulnerability in Digital Music Pad, published on 21 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-2010-20111 exists.

Affected product: Digital Music Pad. 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-2010-20111/ (Markdown: https://insights.sbomify.com/CVE-2010-20111/index.md)
```

## Sources

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

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