# CVE-2010-2220: Denial of service in n/a

> Attackers can cause a denial of service in Adobe Flash Media Server via unspecified input validation issues.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qx9v-hvpm-x8mw

## What is CVE-2010-2220?

CVE-2010-2220 is a medium-severity denial of service vulnerability in n/a, published on 11 Aug 2010. It can be exploited over the network, with no action from the victim.

### Official description

Adobe Flash Media Server (FMS) before 3.0.6, and 3.5.x before 3.5.4, allows attackers to cause a denial of service via unspecified vectors, related to an "input validation issue."

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

It affects 2 products.


Products: Adobe Flash Media Server, Adobe Flash Media Server 2.

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

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

## Is CVE-2010-2220 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3635](https://insights.sbomify.com/CVE-2010-3635/): Code injection in n/a (critical 10.0)
- [CVE-2010-2217](https://insights.sbomify.com/CVE-2010-2217/): Code injection in n/a (critical 10.0)
- [CVE-2009-3792](https://insights.sbomify.com/CVE-2009-3792/): Path traversal in n/a (critical 10.0)
- [CVE-2009-3791](https://insights.sbomify.com/CVE-2009-3791/): Denial of service in n/a (high 7.5)
- [CVE-2009-1365](https://insights.sbomify.com/CVE-2009-1365/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2220 is a medium-severity denial of service vulnerability in n/a, published on 11 Aug 2010. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-2220 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-2220/ (Markdown: https://insights.sbomify.com/CVE-2010-2220/index.md)
```

## Sources

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

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