Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2016-5198 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% 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 is an out-of-bounds write issue (CWE-787) stemming from incorrect optimisation assumptions in the V8 JavaScript engine. It affects Google Chrome versions prior to 54.0.2840.90 on Linux, 54.0.2840.85 on Android, and 54.0.2840.87 on Windows and Mac. The flaw permits arbitrary read and write operations when a victim visits a malicious page.
A remote attacker can exploit the issue by serving a crafted HTML page that triggers the optimisation error during JavaScript execution. Successful exploitation grants the attacker the ability to read or write arbitrary memory, which can be leveraged for remote code execution within the renderer process. The attack requires no user privileges beyond normal web browsing and is rated 8.8 under CVSS 3.1.
Vendor advisories, including the Chrome stable channel update and corresponding Red Hat, SecurityFocus, and SecurityTracker entries, direct users to upgrade to the fixed releases listed above. The Chromium bug tracker entry (crbug.com/659475) further confirms that the patch corrects the optimisation logic to eliminate the invalid memory access assumptions.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2016-6149
Vulnerability Data
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac included incorrect optimisation assumptions, which allowed a remote attacker to perform arbitrary read/write operations, leading to code execution, via a crafted…
more
HTML page.
- CWE(s)
- KEV Date Added
- 08 June 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.