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

> Remote attackers can execute arbitrary code or cause denial of service via crafted Flash content exploiting a use-after-free flaw in Adobe Flash Player.

- **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)
- **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:** 8 Jul 2015
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-3792-ff84-674w, UBUNTU-CVE-2015-5119

## What is CVE-2015-5119?

CVE-2015-5119 is a high-severity use after free vulnerability in Adobe Flash Player, published on 8 Jul 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 the ByteArray class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13.x through 13.0.0.296 and 14.x through 18.0.0.194 on Windows and OS X and 11.x through 11.2.202.468 on Linux allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted Flash content that overrides a valueOf function, as exploited in the wild in July 2015.

Weakness: CWE-416 (Use After Free)

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

It affects 11 products.


Products: Adobe Flash Player, Opensuse Evergreen, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, 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-5119?

Apply the vendor's patch. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2015-5119 being exploited?

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

Public exploit code:

- Archive from the article CVE-2015-5119 Flash ByteArray UaF: A beginner's walkthrough (github_poc): https://github.com/CiscoCXSecurity/CVE-2015-5119_walkthrough
- https://github.com/jvazquez-r7/CVE-2015-5119 (github_poc): https://github.com/jvazquez-r7/CVE-2015-5119
- https://github.com/dangokyo/CVE-2015-5119 (github_poc): https://github.com/dangokyo/CVE-2015-5119
- Adobe Flash Player ByteArray Use After Free (metasploit)
- Adobe Flash Player - ByteArray 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-5119 and fix it if it is affected.

What it is: CVE-2015-5119 is a high-severity use after free vulnerability in Adobe Flash Player, published on 8 Jul 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-5119 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-2015-5119/ (Markdown: https://insights.sbomify.com/CVE-2015-5119/index.md)
```

## Sources

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

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