CVE-2012-0754
Adobe Flash Player Memory Corruption Vulnerability
Adobe Flash Player
Adobe Flash Player before 10.3.183.15 and 11.x before 11.1.102.62 on Windows, Mac OS X, Linux, and Solaris; before 11.1.111.6 on Android 2.x and 3.x; and before 11.1.115.6 on Android 4.x allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 8 June 2022. US federal agencies were required to remediate it by 22 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 91.2%, which is higher than 99.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2012-0754 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2012-0754.
What does CVE-2012-0754 affect?
CVE-2012-0754 affects Adobe Flash Player. Adobe Flash Player before 10.3.183.15 and 11.x before 11.1.102.62 on Windows, Mac OS X, Linux, and Solaris; before 11.1.111.6 on Android 2.x and 3.x; and before 11.1.115.6 on Android 4.x allows attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors.
How severe is CVE-2012-0754?
CVE-2012-0754 is rated HIGH with a CVSS base score of 8.1. EPSS puts the probability of exploitation in the next 30 days at 91.2%, higher than 99.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 22 June 2022.
How should organisations respond to CVE-2012-0754?
Apply the vendor patch for Adobe Flash Player as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.