# CVE-2015-0310: Adobe Flash Player ASLR Bypass

> Attackers can bypass ASLR protection by discovering memory addresses in Adobe Flash Player, facilitating further 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 25 May 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:** 23 Jan 2015
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-3qq4-w757-rjqm, UBUNTU-CVE-2015-0310

## What is CVE-2015-0310?

CVE-2015-0310 is a high-severity vulnerability in Adobe Flash Player, published on 23 Jan 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 before 13.0.0.262 and 14.x through 16.x before 16.0.0.287 on Windows and OS X and before 11.2.202.438 on Linux does not properly restrict discovery of memory addresses, which allows attackers to bypass the ASLR protection mechanism on Windows, and have an unspecified impact on other platforms, via unknown vectors, as exploited in the wild in January 2015.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Adobe Flash Player.

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

Upgrade to a fixed version. US federal agencies must fix it by 15 Jun 2022.

## Is CVE-2015-0310 being exploited?

Yes. Attackers have exploited CVE-2015-0310 in the wild since at least 25 May 2022.

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

What it is: CVE-2015-0310 is a high-severity vulnerability in Adobe Flash Player, published on 23 Jan 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-0310 in the wild since at least 25 May 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-0310/ (Markdown: https://insights.sbomify.com/CVE-2015-0310/index.md)
```

## Sources

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

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