# CVE-2011-0611: Adobe Flash Player Remote Code Execution

> Remote attackers can execute arbitrary code or cause denial of service via crafted Flash content exploiting type confusion in Adobe Flash Player and Reader.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Apr 2011
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-xhq8-8cqj-q337, RHSA-2011:0451

## What is CVE-2011-0611?

CVE-2011-0611 is a high-severity memory corruption vulnerability in Adobe Acrobat, published on 13 Apr 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

Adobe Flash Player before 10.2.154.27 on Windows, Mac OS X, Linux, and Solaris and 10.2.156.12 and earlier on Android; Adobe AIR before 2.6.19140; and Authplay.dll (aka AuthPlayLib.bundle) 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 allow remote attackers to execute arbitrary code or cause a denial of service (application crash) via crafted Flash content; as demonstrated by a Microsoft Office document with an embedded .swf file that has a size inconsistency in a "group of included constants," object type confusion, ActionScript that adds custom functions to prototypes, and Date objects; and as exploited in the wild in April 2011.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

It affects 7 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `flash-plugin` | Red Hat:rhel_extras:5::client | All versions | 0:10.2.159.1-1.el5 |
| `flash-plugin` | Red Hat:rhel_extras:5::server | All versions | 0:10.2.159.1-1.el5 |
| `flash-plugin` | Red Hat:rhel_extras:6 | All versions | 0:10.2.159.1-1.el6 |

Products: Adobe Acrobat, Adobe Acrobat Reader, Adobe Adobe Air, Adobe Flash Player, Google Chrome, Opensuse Opensuse, Suse Linux Enterprise Desktop.

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

Upgrade to a fixed version. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2011-0611 being exploited?

Yes. Attackers have exploited CVE-2011-0611 in the wild since at least 3 Mar 2022.

Public exploit code:

- Adobe Flash Player 10.2.153.1 SWF Memory Corruption Vulnerability (metasploit)
- Adobe Flash Player 10.2.153.1 - SWF Memory Corruption (Metasploit) (exploitdb)
- Adobe Reader X 10.0.0 < 10.0.1 - Atom Type Confusion (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-2011-0611 and fix it if it is affected.

What it is: CVE-2011-0611 is a high-severity memory corruption vulnerability in Adobe Acrobat, published on 13 Apr 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: Yes. Attackers have exploited CVE-2011-0611 in the wild since at least 3 Mar 2022.

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

## Sources

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

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