CVE-2014-0502

KEVAdobe Flash Player Double Free Vulnerablity

Description

Adobe Flash Player contains a double free vulnerability that allows a remote attacker to execute arbitrary code.

Double free vulnerability in Adobe Flash Player before 11.7.700.269 and 11.8.x through 12.0.x before 12.0.0.70 on Windows and Mac OS X and before 11.2.202.341 on Linux, Adobe AIR before 4.0.0.1628 on Android, Adobe AIR SDK before 4.0.0.1628, and Adobe AIR SDK & Compiler before 4.0.0.1628 allows remote attackers to execute arbitrary code via unspecified vectors, as exploited in the wild in February 2014.

CVSS 3.1 vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

PublishedFeb 21, 2014

Last modifiedJun 17, 2026

Added to KEVSep 17, 2024

Remediation dueOct 8, 2024

References

helpx.adobe.com/security/products/flash-player/apsb14-07.htmlBroken LinkPatch
lists.opensuse.org/opensuse-security-announce/2014-02/msg00014.htmlMailing List
lists.opensuse.org/opensuse-security-announce/2014-02/msg00015.htmlMailing List
lists.opensuse.org/opensuse-security-announce/2014-02/msg00017.htmlMailing List
rhn.redhat.com/errata/RHSA-2014-0196.htmlThird Party Advisory
security.gentoo.org/glsa/glsa-201405-04.xmlThird Party Advisory
alienvault.com/open-threat-exchange/blog/analysis-of-an-attack-exploiting-the-adobe-zero-day-cve-2014-0502/ExploitThird Party Advisory
volatility-labs.blogspot.com/2014/04/building-decoder-for-cve-2014-0502.htmlExploitThird Party Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-0502US Government Resource

0 recent articles mention this CVE

Risk assessment · High

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 748 days
CVSS: 8.8 HIGH
EPSS (30-day exploit probability): 24.8% · top 2% of all CVEs
Weakness: CWE-415
Attack vector: Network, remotely reachable

Recommended actions

1.The impacted product is end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue utilization of the product.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.