# CVE-2014-0497: Adobe Flash Player Integer Underflow Vulnerablity

> Remote attackers can execute arbitrary code via an integer underflow vulnerability in Adobe Flash Player.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 17 Sep 2024 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Feb 2014
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-qx9j-q623-p5fh, MGASA-2014-0035, RHSA-2014:0137

## What is CVE-2014-0497?

CVE-2014-0497 is a high-severity vulnerability in Adobe Flash Player, published on 5 Feb 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

Integer underflow in Adobe Flash Player before 11.7.700.261 and 11.8.x through 12.0.x before 12.0.0.44 on Windows and Mac OS X, and before 11.2.202.336 on Linux, allows remote attackers to execute arbitrary code via unspecified vectors.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound))

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

It affects 9 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `flash-plugin` | Red Hat:rhel_extras:5::client | All versions | 0:11.2.202.336-1.el5 |
| `flash-plugin` | Red Hat:rhel_extras:5::server | All versions | 0:11.2.202.336-1.el5 |
| `flash-plugin` | Red Hat:rhel_extras:6 | All versions | 0:11.2.202.336-1.el6 |

Products: Adobe Flash Player, Google Chrome, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Workstation, Suse Linux Enterprise Desktop.

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

Upgrade to a fixed version. US federal agencies must fix it by 8 Oct 2024.

## Is CVE-2014-0497 being exploited?

Yes. Attackers have exploited CVE-2014-0497 in the wild since at least 17 Sep 2024.

Public exploit code:

- Adobe Flash Player Integer Underflow Remote Code Execution (metasploit)
- Adobe Flash Player - Integer Underflow Remote Code Execution (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-2013-0643](https://insights.sbomify.com/CVE-2013-0643/): Adobe Flash Player Incorrect Default Permissions (high 8.8, exploited in the wild)
- [CVE-2013-0648](https://insights.sbomify.com/CVE-2013-0648/): Adobe Flash Player Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0497 is a high-severity vulnerability in Adobe Flash Player, published on 5 Feb 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: Yes. Attackers have exploited CVE-2014-0497 in the wild since at least 17 Sep 2024.

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

## Sources

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

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