CVE-2018-6065: Google Chromium V8 Integer Overflow Vulnerability

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

An integer overflow vulnerability exists in the Google Chromium V8 engine when computing the required allocation size for new JavaScript objects. A remote attacker can exploit this via a crafted HTML page to cause heap corruption, potentially leading to arbitrary code execution.

Technologies: Google Chromium V8. Vendors: Google.

Quick answers

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

Timeline

  • 2018-03-06: patched: Stable Channel Update for Desktop (65.0.3325.146) released.
  • 2022-06-08: kev added: Added to CISA Known Exploited Vulnerabilities Catalog.
  • 2022-06-08: disclosed: NVD publication date.
  • 2022-06-08: exploited: Confirmed as exploited in the wild per CISA KEV.

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