Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2017-5070 is a high-severity Type Confusion (CWE-843) 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 a type confusion flaw, assigned CWE-843, in the V8 JavaScript engine within Google Chrome versions prior to 59.0.3071.86 on Linux, Windows, and Mac, and 59.0.3071.92 on Android. It carries a CVSS 3.1 base score of 8.8 and permits a remote attacker to execute arbitrary code inside the renderer sandbox when a user visits a malicious page.
A remote attacker can exploit the issue by serving a crafted HTML page that triggers the type confusion during JavaScript execution. Successful exploitation yields arbitrary code execution within the Chrome sandbox, with the attack vector requiring user interaction such as navigating to the page but no prior authentication or privileges.
Chrome stable channel updates and corresponding Red Hat errata RHSA-2017:1399 address the flaw by advancing affected installations to the fixed versions listed above; additional vendor trackers including SecurityFocus BID 98861 and SecurityTracker 1038622 reference the same remediation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2017-14179
Vulnerability Data
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted 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
Control response
—
—
—
V1.5.2V3.2.3V15.3.5
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 SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.
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 can detect type-confusion vulnerabilities through fuzzing and static analysis.
Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.
Application security requirements can specify strong typing and interface contracts that reduce type confusion.
Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.
Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.