How severe is CVE-2014-0515?

No CVSS score has been assigned to CVE-2014-0515 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-0515?

Affected package information for CVE-2014-0515 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2014-0515?

No fixed release is recorded for CVE-2014-0515 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2014-0515 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2014-0515 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2014-0515 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-0515, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-0515?

CVE-2014-0515 has an EPSS (Exploit Prediction Scoring System) score of 94.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2014-0515?

CVE-2014-0515 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-0515 published, and has it been updated?

CVE-2014-0515 was published on April 29, 2014 and was last updated on August 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2014-0515 — Red Hat

CVE-2014-0515 is a Buffer Overflow vulnerability. 3 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Buffer overflow in Adobe Flash Player before 11.7.700.279 and 11.8.x through 13.0.x before 13.0.0.206 on Windows and OS X, and before 11.2.202.356 on Linux, allows remote attackers…

Published

Apr 29, 2014

Updated

Aug 6, 2024

Affected

1 product

Patched

See advisory

Exploits

3 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

94.5%probability of exploitation in next 30 days

Very High Risk-0.08%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Buffer overflow in Adobe Flash Player before 11.7.700.279 and 11.8.x through 13.0.x before 13.0.0.206 on Windows and OS X, and before 11.2.202.356 on Linux, allows remote attackers to execute arbitrary code via unspecified vectors, as exploited in the wild in April 2014.

Affected Products

1 product · 3 configurations

Application

flash playeradobe

≥ 11.8 && < 13.0.0.206

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-33333remotewindows✓ Verified

Adobe Flash Player - Shader Buffer Overflow (Metasploit)

by Metasploit · May 12, 2014

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2014-0515 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Product	Fixed in	Advisory
Supplementary for Red Hat Enterprise Linux 5	`flash-plugin-0:11.2.202.356-1.el5`	RHSA-2014:0447

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0515 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works