# CVE-2011-0610: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via memory corruption in Adobe Reader and Acrobat.

- **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:** No
- **Published:** 3 May 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wp4v-3h93-jx8x

## What is CVE-2011-0610?

CVE-2011-0610 is a critical memory corruption vulnerability in Adobe Acrobat, published on 3 May 2011. 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

The CoolType library in Adobe Reader 9.x before 9.4.4 and 10.x through 10.0.1 on Windows, Adobe Reader 9.x before 9.4.4 and 10.x before 10.0.3 on Mac OS X, and Adobe Acrobat 9.x before 9.4.4 and 10.x before 10.0.3 on Windows and Mac OS X allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 2 products.


Products: Adobe Acrobat, Adobe Acrobat Reader.

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

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

## Is CVE-2011-0610 being exploited?

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

## 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-2011-0610 and fix it if it is affected.

What it is: CVE-2011-0610 is a critical memory corruption vulnerability in Adobe Acrobat, published on 3 May 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-0610 in the wild and no public exploit code.

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

## Sources

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

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