# CVE-2010-2201: Memory corruption in n/a

> Attackers can execute arbitrary code by tricking users into opening a malicious PDF file with crafted Flash content in Adobe Reader.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qm3q-8q36-x3vh

## What is CVE-2010-2201?

CVE-2010-2201 is a critical memory corruption vulnerability in Adobe Acrobat, published on 30 Jun 2010. 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

Adobe Reader and Acrobat 9.x before 9.3.3, and 8.x before 8.2.3 on Windows and Mac OS X, allow attackers to execute arbitrary code via a PDF file with crafted Flash content involving the (1) pushstring (0x2C) operator, (2) debugfile (0xF1) operator, and an "invalid pointer vulnerability" that triggers memory corruption, a different vulnerability than CVE-2010-1285 and CVE-2010-2168.

Weakness: CWE-399

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

It affects 2 products.


Products: Adobe Acrobat, Adobe Acrobat Reader.

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

Upgrade to a fixed version.

## Is CVE-2010-2201 being exploited?

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

Public exploit code:

- Adobe Acrobat and Reader - 'pushstring' Memory Corruption (exploitdb)

## Other vulnerabilities in Adobe Acrobat

- [CVE-2021-28550](https://insights.sbomify.com/CVE-2021-28550/): Adobe Acrobat and Reader Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2021-21017](https://insights.sbomify.com/CVE-2021-21017/): Adobe Acrobat and Reader Heap-based Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2014-0546](https://insights.sbomify.com/CVE-2014-0546/): Adobe Reader and Acrobat Sandbox Bypass (high 8.8, exploited in the wild)
- [CVE-2014-0496](https://insights.sbomify.com/CVE-2014-0496/): Adobe Reader and Acrobat Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2013-3346](https://insights.sbomify.com/CVE-2013-3346/): Adobe Reader and Acrobat Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-2201 is a critical memory corruption vulnerability in Adobe Acrobat, published on 30 Jun 2010. 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-2010-2201 exists.

Affected product: Adobe Acrobat. 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-2201/ (Markdown: https://insights.sbomify.com/CVE-2010-2201/index.md)
```

## Sources

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

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