606
VMScore

CVE-2017-15428

Published: 09/01/2019 Updated: 07/11/2023
CVSS v2 Base Score: 6.8 | Impact Score: 6.4 | Exploitability Score: 8.6
CVSS v3 Base Score: 8.8 | Impact Score: 5.9 | Exploitability Score: 2.8
VMScore: 606
Vector: AV:N/AC:M/Au:N/C:P/I:P/A:P

Vulnerability Summary

Insufficient data validation in V8 builtins string generator could lead to out of bounds read and write access in V8 in Google Chrome before 62.0.3202.94 and allowed a remote malicious user to execute arbitrary code inside a sandbox via a crafted HTML page.

Vulnerability Trend

Vulnerable Product Search on Vulmon Subscribe to Product

google chrome

Github Repositories

An exploit for CVE-2017-15428

CVE-2017-15428 This is an exploit for the V8 vulnerability CVE-2017-15428, which was discovered in 2017 by Zhao Qixun (@S0rryMybad) of the Qihoo 360 Vulcan Team I did not have any involvement in the discovery of this bug This exploit was written as part of my final year thesis at university

V8_November_2017 Some V8 vuls which they were fixed in about November 2017 CVE-2017-5070 bugschromiumorg/p/chromium/issues/detail?id=722756 Chrome version: 5803029110 Channel: stable This problem belongs to the crankshaft,in the latest V8 version(16th May 2017)(use crankshaft to JIT),I can reproduce this issueAt this version,the chrome use crankshaft to JIT CVE-