# CVE-2015-8442: Use after free in n/a

> Attackers can execute arbitrary code via a crafted filters property value in Adobe Flash Player, requiring user interaction to view malicious content.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3cx9-j5vf-23wp, UBUNTU-CVE-2015-8442

## What is CVE-2015-8442?

CVE-2015-8442 is a critical use after free vulnerability in Adobe Air, published on 10 Dec 2015. 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

Use-after-free vulnerability in the MovieClip object implementation in Adobe Flash Player before 18.0.0.268 and 19.x and 20.x before 20.0.0.228 on Windows and OS X and before 11.2.202.554 on Linux, Adobe AIR before 20.0.0.204, Adobe AIR SDK before 20.0.0.204, and Adobe AIR SDK & Compiler before 20.0.0.204 allows attackers to execute arbitrary code via a crafted filters property value, a different vulnerability than CVE-2015-8048, CVE-2015-8049, CVE-2015-8050, CVE-2015-8055, CVE-2015-8056, CVE-2015-8057, CVE-2015-8058, CVE-2015-8059, CVE-2015-8061, CVE-2015-8062, CVE-2015-8063, CVE-2015-8064, CVE-2015-8065, CVE-2015-8066, CVE-2015-8067, CVE-2015-8068, CVE-2015-8069, CVE-2015-8070, CVE-2015-8071, CVE-2015-8401, CVE-2015-8402, CVE-2015-8403, CVE-2015-8404, CVE-2015-8405, CVE-2015-8406, CVE-2015-8410, CVE-2015-8411, CVE-2015-8412, CVE-2015-8413, CVE-2015-8414, CVE-2015-8420, CVE-2015-8421, CVE-2015-8422, CVE-2015-8423, CVE-2015-8424, CVE-2015-8425, CVE-2015-8426, CVE-2015-8427, CVE-2015-8428, CVE-2015-8429, CVE-2015-8430, CVE-2015-8431, CVE-2015-8432, CVE-2015-8433, CVE-2015-8434, CVE-2015-8435, CVE-2015-8436, CVE-2015-8437, CVE-2015-8441, CVE-2015-8447, CVE-2015-8448, CVE-2015-8449, CVE-2015-8450, CVE-2015-8452, and CVE-2015-8454.

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

It affects 4 products.


Products: Adobe Air, Adobe Air Sdk, Adobe Air Sdk \& Compiler, Adobe Flash Player.

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

Upgrade to a fixed version.

## Is CVE-2015-8442 being exploited?

There is no known exploitation of CVE-2015-8442 in the wild and no public exploit code.

## Other vulnerabilities in Adobe Air

- [CVE-2016-1010](https://insights.sbomify.com/CVE-2016-1010/): Adobe Flash Player and AIR Integer Overflow (high 8.8, exploited in the wild)
- [CVE-2015-8651](https://insights.sbomify.com/CVE-2015-8651/): Adobe Flash Player Integer Overflow (high 8.8, exploited in the wild)
- [CVE-2014-8439](https://insights.sbomify.com/CVE-2014-8439/): Adobe Flash Player Dereferenced Pointer (high 8.8, exploited in the wild)
- [CVE-2012-2034](https://insights.sbomify.com/CVE-2012-2034/): Adobe Flash Player Memory Corruption (high 7.5, exploited in the wild)
- [CVE-2015-8459](https://insights.sbomify.com/CVE-2015-8459/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8442 is a critical use after free vulnerability in Adobe Air, published on 10 Dec 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-8442 in the wild and no public exploit code.

Affected product: Adobe Air. 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-8442/ (Markdown: https://insights.sbomify.com/CVE-2015-8442/index.md)
```

## Sources

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

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