Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2016-1646 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Canonical Ubuntu Linux. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2016-1646 is an out-of-bounds read (CWE-125) in the Array.prototype.concat implementation within builtins.cc in Google V8, as used in Google Chrome before version 49.0.2623.108. The root cause is failure to properly account for element data types during array concatenation operations.
Remote attackers can exploit the issue by serving crafted JavaScript to a victim, triggering the flaw to cause a denial of service or potentially other unspecified impacts. The CVSS 3.1 score of 8.8 reflects network attack vector, low complexity, no privileges or user interaction required beyond rendering the script, and high impact on confidentiality, integrity, and availability.
Public advisories and patches referenced in the Google Chrome stable channel update, multiple openSUSE security announcements, and Red Hat errata RHSA-2016-0525 address mitigation by updating affected V8 and Chrome installations to corrected versions. No information on observed in-the-wild exploitation is provided in the source details.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2016-2741
Vulnerability Data
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…
more
via crafted JavaScript code.
- CWE(s)
- KEV Date Added
- 08 June 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.