# CVE-2017-11292: Adobe Flash Player Type Confusion

> A type confusion vulnerability in Adobe Flash Player allows attackers to execute arbitrary code via crafted content.

- **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:** 21 Oct 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-f6x6-gf9m-8cc3, MGASA-2017-0377, RHSA-2017:2899, UBUNTU-CVE-2017-11292

## What is CVE-2017-11292?

CVE-2017-11292 is a high-severity memory corruption vulnerability in Adobe Flash Player, published on 21 Oct 2017. 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 version 27.0.0.159 and earlier has a flawed bytecode verification procedure, which allows for an untrusted value to be used in the calculation of an array index. This can lead to type confusion, and successful exploitation could lead to arbitrary code execution.

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

## Which versions are affected by CVE-2017-11292?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `flash-plugin` | Red Hat:rhel_extras:6 | All versions | 0:27.0.0.170-1.el6_9 |

Products: Adobe Flash Player, Adobe Flash Player Desktop Runtime, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2017-11292?

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

## Is CVE-2017-11292 being exploited?

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

## Other vulnerabilities in Adobe Flash Player

- [CVE-2016-7892](https://insights.sbomify.com/CVE-2016-7892/): Adobe Flash Player Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2016-7855](https://insights.sbomify.com/CVE-2016-7855/): Adobe Flash Player Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2014-0497](https://insights.sbomify.com/CVE-2014-0497/): Adobe Flash Player Integer Underflow Vulnerablity (high 8.8, exploited in the wild)
- [CVE-2013-0643](https://insights.sbomify.com/CVE-2013-0643/): Adobe Flash Player Incorrect Default Permissions (high 8.8, exploited in the wild)
- [CVE-2013-0648](https://insights.sbomify.com/CVE-2013-0648/): Adobe Flash Player Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11292 and fix it if it is affected.

What it is: CVE-2017-11292 is a high-severity memory corruption vulnerability in Adobe Flash Player, published on 21 Oct 2017. 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-2017-11292 in the wild since at least 3 Mar 2022.

Affected product: Adobe Flash Player. 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-2017-11292/ (Markdown: https://insights.sbomify.com/CVE-2017-11292/index.md)
```

## Sources

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

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