# CVE-2018-15982: Adobe Flash Player Use-After-Free

> Attackers can execute arbitrary code via a use-after-free flaw in Adobe Flash Player, requiring users to update the plugin.

- **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 15 Feb 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:** 18 Jan 2019
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-26v8-ffh8-7vqg, RHSA-2018:3795, UBUNTU-CVE-2018-15982

## What is CVE-2018-15982?

CVE-2018-15982 is a high-severity use after free vulnerability in Adobe Flash Player, published on 18 Jan 2019. 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

Flash Player versions 31.0.0.153 and earlier, and 31.0.0.108 and earlier have a use after free vulnerability. Successful exploitation could lead to arbitrary code execution.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2018-15982?

It affects 5 products.


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

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

## How do I fix CVE-2018-15982?

Apply the vendor's patch. US federal agencies must fix it by 15 Aug 2022.

## Is CVE-2018-15982 being exploited?

Yes. Attackers have exploited CVE-2018-15982 in the wild since at least 15 Feb 2022, including in ransomware campaigns.

Public exploit code:

- exp of CVE-2018-15982 (github_poc): https://github.com/Ridter/CVE-2018-15982_EXP
- Aggressor Script to launch IE driveby for CVE-2018-15982. (github_poc): https://github.com/scanfsec/CVE-2018-15982
- CVE-2018-15982_PoC (github_poc): https://github.com/Ormicron/CVE-2018-15982_PoC
- CVE-2018-15982_EXP_IE (github_poc): https://github.com/jas502n/CVE-2018-15982_EXP_IE
- Script and metasploit module for CVE-2018-15982 (github_poc): https://github.com/kphongagsorn/adobe-flash-cve2018-15982
- Flash 2018-15982 UAF  (github_poc): https://github.com/SyFi/CVE-2018-15982

## 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-2018-15982 and fix it if it is affected.

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

## Sources

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

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