CVE-2014-8439
KEVAdobe Flash Player Dereferenced Pointer Vulnerability
Description
Adobe Flash Player has a vulnerability in the way it handles a dereferenced memory pointer which could lead to code execution.
Adobe Flash Player before 13.0.0.258 and 14.x and 15.x before 15.0.0.239 on Windows and OS X and before 11.2.202.424 on Linux, Adobe AIR before 15.0.0.293, Adobe AIR SDK before 15.0.0.302, and Adobe AIR SDK & Compiler before 15.0.0.302 allow attackers to execute arbitrary code or cause a denial of service (invalid pointer dereference) via unspecified vectors.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HPublishedNov 25, 2014
Last modifiedJun 17, 2026
Added to KEVMay 25, 2022
Remediation dueJun 15, 2022
References
- helpx.adobe.com/security/products/flash-player/apsb14-22.htmlVendor Advisory
- helpx.adobe.com/security/products/flash-player/apsb14-26.htmlVendor Advisory
- lists.opensuse.org/opensuse-security-announce/2014-11/msg00020.htmlThird Party Advisory
- lists.opensuse.org/opensuse-security-announce/2014-12/msg00001.htmlThird Party Advisory
- lists.opensuse.org/opensuse-security-announce/2014-12/msg00004.htmlThird Party Advisory
- rhn.redhat.com/errata/RHSA-2014-1915.htmlVendor Advisory
- secunia.com/advisories/60217Permissions Required
- securityfocus.com/bid/71289Third Party AdvisoryVDB Entry
- securitytracker.com/id/1031259Third Party AdvisoryVDB Entry
- exchange.xforce.ibmcloud.com/vulnerabilities/98932Third Party AdvisoryVDB Entry
- f-secure.com/weblog/archives/00002768.htmlThird Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2014-8439US Government Resource
0 recent articles mention this CVE
76
Risk assessment · High
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1594 days
- CVSS
- 8.8 HIGH
- EPSS (30-day exploit probability)
- 20.4% · top 3% of all CVEs
- Weakness
- CWE-119
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.The impacted product is end-of-life and should be disconnected if still in use.
- 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.