# CVE-2015-7645: Adobe Flash Player Arbitrary Code Execution

> Remote attackers can execute arbitrary code via crafted SWF files in Adobe Flash Player, requiring immediate upgrades to mitigate active exploitation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Oct 2015
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-67j3-p5pq-jgr7, SUSE-SU-2015:1770-1, SUSE-SU-2015:1771-1, UBUNTU-CVE-2015-7645

## What is CVE-2015-7645?

CVE-2015-7645 is a high-severity code injection vulnerability in Adobe Flash Player, published on 15 Oct 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Adobe Flash Player 18.x through 18.0.0.252 and 19.x through 19.0.0.207 on Windows and OS X and 11.x through 11.2.202.535 on Linux allows remote attackers to execute arbitrary code via a crafted SWF file, as exploited in the wild in October 2015.

## Which versions are affected by CVE-2015-7645?

It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `flash-player` | SUSE:Linux Enterprise Desktop 11 SP3 | All versions | 11.2.202.540-0.23.1 |
| `flash-player` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 11.2.202.540-0.23.1 |
| `flash-player` | SUSE:Linux Enterprise Desktop 12 | All versions | 11.2.202.540-108.1 |
| `flash-player` | SUSE:Linux Enterprise Workstation Extension 12 | All versions | 11.2.202.540-108.1 |

Products: Adobe Flash Player, Opensuse Evergreen, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server From Rhui, Redhat Enterprise Linux Workstation, Suse Linux Enterprise Desktop, Suse Linux Enterprise Workstation Extension.

## How do I fix CVE-2015-7645?

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

## Is CVE-2015-7645 being exploited?

Yes. Attackers have exploited CVE-2015-7645 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

Public exploit code:

- Adobe Flash - 'IExternalizable.writeExternal' Type Confusion (exploitdb)

## Other vulnerabilities in Adobe Flash Player

- [CVE-2017-11292](https://insights.sbomify.com/CVE-2017-11292/): Adobe Flash Player Type Confusion (high 8.8, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7645 and fix it if it is affected.

What it is: CVE-2015-7645 is a high-severity code injection vulnerability in Adobe Flash Player, published on 15 Oct 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2015-7645 in the wild since at least 3 Mar 2022, including in ransomware campaigns.

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

## Sources

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

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