CVE-2016-1646
Google Chromium V8 Out-of-Bounds Read
- Published29 Mar 2016
- Added to CISA KEV8 Jun 2022
- Remediation due22 Jun 2022
Description
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, does not properly consider element data types, which allows remote attackers to cause a denial of service (out-of-bounds read) or possibly have unspecified other impact via crafted JavaScript code.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- http://googlechromereleases.blogspot.com/2016/03/stable-channel-update_24.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00000.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00001.html
- http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00039.html
- http://rhn.redhat.com/errata/RHSA-2016-0525.html
- https://code.google.com/p/chromium/issues/detail?id=594574
- https://codereview.chromium.org/1804963002/
- https://security.gentoo.org/glsa/201605-02
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2016-1646
- http://www.debian.org/security/2016/dsa-3531
and 2 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2016-1646 being actively exploited?
Yes. CVE-2016-1646 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 8 Jun 2022.
How severe is CVE-2016-1646?
CVE-2016-1646 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 48.1% probability of exploitation.
Which products are affected by CVE-2016-1646?
Affected products include Google Chrome, Suse Package Hub, Canonical Ubuntu Linux, Debian Linux, Opensuse Leap, and 5 more.
How do I fix CVE-2016-1646?
Upgrade affected software to a fixed version, for example Google Chrome 49.0.2623.108 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2016-1646 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.