# CVE-2015-0313: Adobe Flash Player Use-After-Free

> Remote attackers can execute arbitrary code via a use-after-free vulnerability in Adobe Flash Player, requiring users to upgrade immediately.

- **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 13 Apr 2022 (CISA KEV)
- **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:** 2 Feb 2015
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-fg66-4vpm-36cx, UBUNTU-CVE-2015-0313

## What is CVE-2015-0313?

CVE-2015-0313 is a high-severity use after free vulnerability in Adobe Flash Player, published on 2 Feb 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

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.269 and 14.x through 16.x before 16.0.0.305 on Windows and OS X and before 11.2.202.442 on Linux allows remote attackers to execute arbitrary code via unspecified vectors, as exploited in the wild in February 2015, a different vulnerability than CVE-2015-0315, CVE-2015-0320, and CVE-2015-0322.

Weakness: CWE-416 (Use After Free)

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

It affects 7 products.


Products: Adobe Flash Player, Microsoft Edge, Microsoft Internet Explorer, Opensuse Evergreen, Opensuse Opensuse, Suse Linux Enterprise Desktop, Suse Linux Enterprise Workstation Extension.

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

Upgrade to a fixed version. US federal agencies must fix it by 4 May 2022.

## Is CVE-2015-0313 being exploited?

Yes. Attackers have exploited CVE-2015-0313 in the wild since at least 13 Apr 2022.

Public exploit code:

- https://github.com/SecurityObscurity/cve-2015-0313 (github_poc): https://github.com/SecurityObscurity/cve-2015-0313
- Adobe Flash Player ByteArray With Workers Use After Free (metasploit)
- Adobe Flash Player - Arbitrary Code Execution (exploitdb)
- Adobe Flash Player - ByteArray With Workers Use-After-Free (Metasploit) (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-0313 and fix it if it is affected.

What it is: CVE-2015-0313 is a high-severity use after free vulnerability in Adobe Flash Player, published on 2 Feb 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-0313 in the wild since at least 13 Apr 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-2015-0313/ (Markdown: https://insights.sbomify.com/CVE-2015-0313/index.md)
```

## Sources

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

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