# CVE-2014-0551: Memory corruption in n/a

> Attackers can execute arbitrary code or cause denial of service via memory corruption in Adobe Flash Player, requiring user interaction to view malicious content.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9mp9-986f-x852, UBUNTU-CVE-2014-0551

## What is CVE-2014-0551?

CVE-2014-0551 is a critical memory corruption vulnerability in Adobe Adobe Air, published on 10 Sep 2014. 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

Adobe Flash Player before 13.0.0.244 and 14.x and 15.x before 15.0.0.152 on Windows and OS X and before 11.2.202.406 on Linux, Adobe AIR before 15.0.0.249 on Windows and OS X and before 15.0.0.252 on Android, Adobe AIR SDK before 15.0.0.249, and Adobe AIR SDK & Compiler before 15.0.0.249 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-0547, CVE-2014-0549, CVE-2014-0550, CVE-2014-0552, and CVE-2014-0555.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2014-0551?

It affects 3 products.


Products: Adobe Adobe Air, Adobe Adobe Air Sdk, Adobe Flash Player.

## How do I fix CVE-2014-0551?

Upgrade to a fixed version.

## Is CVE-2014-0551 being exploited?

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

## Other vulnerabilities in Adobe Adobe Air

- [CVE-2014-0502](https://insights.sbomify.com/CVE-2014-0502/): Adobe Flash Player Double Free Vulnerablity (high 8.8, exploited in the wild)
- [CVE-2015-0301](https://insights.sbomify.com/CVE-2015-0301/): Other in n/a (critical 10.0)
- [CVE-2015-0303](https://insights.sbomify.com/CVE-2015-0303/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0304](https://insights.sbomify.com/CVE-2015-0304/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-0306](https://insights.sbomify.com/CVE-2015-0306/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0551 and fix it if it is affected.

What it is: CVE-2014-0551 is a critical memory corruption vulnerability in Adobe Adobe Air, published on 10 Sep 2014. 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-2014-0551 in the wild and no public exploit code.

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

## Sources

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

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