# CVE-2010-3085: Code injection in n/a

> Remote attackers can execute arbitrary code on Mednafen emulator users via malicious network-play interactions.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2010
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2010-3085, GHSA-rr8f-99gv-42p7

## What is CVE-2010-3085?

CVE-2010-3085 is a critical code injection vulnerability in n/a, published on 12 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The network-play implementation in Mednafen before 0.8.D might allow remote servers to execute arbitrary code via unspecified vectors, related to "stack manipulation" issues.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: David Shadoff Mednafen.

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

Upgrade to a fixed version.

## Is CVE-2010-3085 being exploited?

There is no known exploitation of CVE-2010-3085 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2010-3085 is a critical code injection vulnerability in n/a, published on 12 Oct 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-3085 in the wild and no public exploit code.

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-2010-3085/ (Markdown: https://insights.sbomify.com/CVE-2010-3085/index.md)
```

## Sources

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

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