# CVE-2015-3043: Adobe Flash Player Memory Corruption

> Attackers can execute arbitrary code or cause denial of service via memory corruption in Adobe Flash Player, requiring immediate upgrades.

- **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:** 14 Apr 2015
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-68qr-58pp-42rr, UBUNTU-CVE-2015-3043

## What is CVE-2015-3043?

CVE-2015-3043 is a high-severity memory corruption vulnerability in Adobe Flash Player, published on 14 Apr 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.281 and 14.x through 17.x before 17.0.0.169 on Windows and OS X and before 11.2.202.457 on Linux allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, as exploited in the wild in April 2015, a different vulnerability than CVE-2015-0347, CVE-2015-0350, CVE-2015-0352, CVE-2015-0353, CVE-2015-0354, CVE-2015-0355, CVE-2015-0360, CVE-2015-3038, CVE-2015-3041, and CVE-2015-3042.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 11 products.


Products: Adobe Flash Player, Novell Suse Linux Enterprise Desktop, Novell Suse Linux Enterprise Workstation Extension, 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.

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

Upgrade to a fixed version. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2015-3043 being exploited?

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

Public exploit code:

- Adobe Flash Player Nellymoser Audio Decoding Buffer Overflow (metasploit)
- Adobe Flash Player - Nellymoser Audio Decoding Buffer Overflow (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-3043 and fix it if it is affected.

What it is: CVE-2015-3043 is a high-severity memory corruption vulnerability in Adobe Flash Player, published on 14 Apr 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-3043 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-3043/ (Markdown: https://insights.sbomify.com/CVE-2015-3043/index.md)
```

## Sources

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

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