CVE-2020-6418: Google Chromium V8 Type Confusion Vulnerability

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

A type confusion vulnerability exists in the Google Chromium V8 engine that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The flaw is triggered when the engine incorrectly handles object types, leading to memory safety issues.

Technologies: Google Chromium V8. Vendors: Google.

Quick answers

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

Timeline

  • 2020-02-24: patched: Stable channel update for desktop (80.0.3987.122) released.
  • 2021-11-03: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.
  • 2021-11-03: disclosed: Publicly disclosed/published date.
  • exploited: Reported as exploited in the wild.

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