CVE-2021-38003: Google Chromium V8 Memory Corruption Vulnerability

CVE-2021-38003 · Severity: critical · CVSS 8.8 · Exploited in the wild · Published 2021-11-03

Google Chromium V8 Engine contains a memory corruption vulnerability due to an inappropriate implementation in JSON.stringify that allows the internal TheHole value to leak to script code. A remote attacker can exploit this heap corruption via a crafted HTML page, potentially affecting all Chromium-based browsers.

Technologies: Google Chromium V8. Vendors: Google.

Quick answers

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

Timeline

  • 2021-10-28: patched: Stable channel update for desktop released (95.0.4638.69)
  • 2021-11-03: disclosed: Vulnerability published and added to CISA KEV catalog
  • 2021-11-03: kev added
  • 2021-11-03: exploited: Reported as exploited in the wild in CISA KEV catalog

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