CVE-2018-17480
Google Chromium V8 Out-of-Bounds Write Vulnerability
Google Chromium V8
Execution of user supplied Javascript during array deserialization leading to an out of bounds write in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to execute arbitrary code inside a sandbox 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 35.6%, which is higher than 98.5% 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-2018-17480 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2018-17480.
What does CVE-2018-17480 affect?
CVE-2018-17480 affects Google Chromium V8. Execution of user supplied Javascript during array deserialization leading to an out of bounds write in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
How severe is CVE-2018-17480?
CVE-2018-17480 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 35.6%, higher than 98.5% 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-2018-17480?
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.