CVE-2016-1646: Google Chromium V8 Out-of-Bounds Read Vulnerability

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

The Array.prototype.concat implementation in builtins.cc in Google V8 Engine does not properly consider element data types. This allows a remote attacker to cause an out-of-bounds read, leading to a denial of service or other unspecified impacts via crafted JavaScript code.

Technologies: Google Chromium V8. Vendors: Google.

Quick answers

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

Timeline

  • 2016-03-24: patched: Stable Channel Update for Google Chrome 49.0.2623.108
  • 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.