CVE-2013-0648
Adobe Flash Player Code Execution Vulnerability
Adobe Flash Player
Unspecified vulnerability in the ExternalInterface ActionScript functionality in Adobe Flash Player before 10.3.183.67 and 11.x before 11.6.602.171 on Windows and Mac OS X, and before 10.3.183.67 and 11.x before 11.2.202.273 on Linux, allows remote attackers to execute arbitrary code via crafted SWF content, as exploited in the wild in February 2013.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 17 September 2024. US federal agencies were required to remediate it by 8 October 2024.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 11.1%, which is higher than 96% 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:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2013-0648 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-0648.
What does CVE-2013-0648 affect?
CVE-2013-0648 affects Adobe Flash Player. Unspecified vulnerability in the ExternalInterface ActionScript functionality in Adobe Flash Player before 10.3.183.67 and 11.x before 11.6.602.171 on Windows and Mac OS X, and before 10.3.183.67 and 11.x before 11.2.202.273 on Linux, allows remote attackers to execute arbitrary code via crafted SWF content, as exploited in the wild in February 2013.
How severe is CVE-2013-0648?
CVE-2013-0648 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 11.1%, higher than 96% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 8 October 2024.
How should organisations respond to CVE-2013-0648?
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.