CVE-2017-5030: Google Chromium V8 Memory Corruption Vulnerability

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

Google Chromium V8 Engine contains a memory corruption vulnerability due to incorrect handling of complex species. A remote attacker can exploit this via a crafted HTML page to execute arbitrary code on the target system.

Technologies: Google Chromium V8. Vendors: Google.

Quick answers

Is CVE-2017-5030 exploited in the wild?
Yes. CVE-2017-5030 is known to be exploited in the wild, first recorded on 8 June 2022. Treat it as urgent.
How severe is CVE-2017-5030?
Critical severity, with a CVSS score of 8.8, published 8 June 2022.
Which products and versions are affected?
Google Chrome prior to 57.0.2987.98; Google Chrome for Android prior to 57.0.2987.108; Google V8 Engine prior to 57.0.2987.98.
Is there a fix for CVE-2017-5030?
A patch was published on 2017-03-09: Stable channel update for desktop released (57.0.2987.98) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2017-5030 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2017-5030?
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 57.0.2987.98
  • Google Chrome for Android prior to 57.0.2987.108
  • Google V8 Engine prior to 57.0.2987.98

Timeline

  • 2017-03-09: patched: Stable channel update for desktop released (57.0.2987.98)
  • 2022-06-08: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
  • 2022-06-08: disclosed

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