CVE-2014-0497
KEVAdobe Flash Player Integer Underflow Vulnerablity
Description
Adobe Flash Player contains an integer underflow vulnerability that allows a remote attacker to execute arbitrary code.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedFeb 5, 2014
Last modifiedJun 17, 2026
Added to KEVSep 17, 2024
Remediation dueOct 8, 2024
References
- googlechromereleases.blogspot.com/2014/02/stable-channel-update.htmlRelease Notes
- helpx.adobe.com/security/products/flash-player/apsb14-04.htmlBroken LinkPatch
- lists.opensuse.org/opensuse-security-announce/2014-02/msg00000.htmlMailing List
- lists.opensuse.org/opensuse-security-announce/2014-02/msg00001.htmlMailing List
- lists.opensuse.org/opensuse-security-announce/2014-02/msg00006.htmlMailing List
- rhn.redhat.com/errata/RHSA-2014-0137.htmlThird Party Advisory
- secunia.com/advisories/56437Broken LinkThird Party Advisory
- secunia.com/advisories/56737Broken LinkThird Party Advisory
- secunia.com/advisories/56780Broken LinkThird Party Advisory
- secunia.com/advisories/56799Broken LinkThird Party Advisory
- secunia.com/advisories/56839Broken LinkThird Party Advisory
- exploit-db.com/exploits/33212Third Party AdvisoryVDB Entry
0 recent articles mention this CVE
89
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 749 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 99.9% · top 1% of all CVEs
- Weakness
- CWE-191
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
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.