# CVE-2011-10022: SPlayer 3.7 Content-Type Header Buffer Overflow

> A stack-based buffer overflow in SPlayer allows remote code execution via a malicious HTTP response when opening media files.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/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:** Over the internet
- **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-6rq9-46gf-5xrp

## What is CVE-2011-10022?

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

SPlayer version 3.7 and earlier is vulnerable to a stack-based buffer overflow when processing HTTP responses containing an overly long Content-Type header. The vulnerability occurs due to improper bounds checking on the header value, allowing an attacker to overwrite the Structured Exception Handler (SEH) and execute arbitrary code. Exploitation requires the victim to open a media file that triggers an HTTP request to a malicious server, which responds with a crafted Content-Type header.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2011-10022 being exploited?

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

Public exploit code:

- SPlayer 3.7 Content-Type Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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