CVE-2017-5030
Google Chromium V8 Memory Corruption Vulnerability
Google Chromium V8
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android allowed a remote attacker to execute arbitrary code via a crafted HTML page.
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 40.6%, which is higher than 98.7% 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-2017-5030 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2017-5030.
What does CVE-2017-5030 affect?
CVE-2017-5030 affects Google Chromium V8. Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android allowed a remote attacker to execute arbitrary code via a crafted HTML page.
How severe is CVE-2017-5030?
CVE-2017-5030 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 40.6%, higher than 98.7% 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-2017-5030?
Apply the vendor patch for Google Chromium V8 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.