CVE-2018-17480: Google Chromium V8 Out-of-Bounds Write Vulnerability

CVE-2018-17480 · Severity: critical · CVSS 8.8 · Exploited in the wild · Published 2022-06-08

Google Chromium V8 Engine contains an out-of-bounds write vulnerability triggered during array deserialization. A remote attacker can exploit this via a crafted HTML page to execute arbitrary code inside the browser sandbox.

Technologies: Google Chromium V8. Vendors: Google.

Quick answers

Is CVE-2018-17480 exploited in the wild?
Yes. CVE-2018-17480 is known to be exploited in the wild, first recorded on 8 June 2022. Treat it as urgent.
How severe is CVE-2018-17480?
Critical severity, with a CVSS score of 8.8, published 8 June 2022.
Which products and versions are affected?
Google Chrome prior to 71.0.3578.80; Google V8 Engine.
Is there a fix for CVE-2018-17480?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2018-17480 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2018-17480?
Check whether you run Google Chromium V8. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • Google Chrome prior to 71.0.3578.80
  • Google V8 Engine

Timeline

  • 2018-12-19: disclosed: Initial analysis by NIST
  • 2022-06-08: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
  • 2022-06-08: exploited: Reported as exploited in the wild

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.