Not rated
CVE-2017-15392 Insufficient data validation in V8 in Google Chrome prior to 62.0.3202.62 allowed an attacker who can write to the…
Description
Insufficient data validation in V8 in Google Chrome prior to 62.0.3202.62 allowed an attacker who can write to the Windows Registry to potentially exploit heap corruption via a crafted Windows Registry entry, related to PlatformIntegration.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Google Chrome prior to 62.0.3202.62 | Versions not published |
References
- 101482 www.securityfocus.com
- chromereleases.googleblog.com chromereleases.googleblog.com
- crbug.com crbug.com
- DSA-4020 www.debian.org
- RHSA-2017:2997 access.redhat.com
- GLSA-201710-24 security.gentoo.org
Timeline
- Published
- Last modified
Other CVEs of Google Chrome prior to 62.0.3202.62
The 20 CVEs of Google Chrome prior to 62.0.3202.62 →
CVE-2017-5125
Heap buffer overflow in Skia in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit…
Not rated
CVE-2017-5127
Use after free in PDFium in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit heap…
Not rated
CVE-2017-5126
A use after free in PDFium in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit…
Not rated
CVE-2017-5128
Heap buffer overflow in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to potentially exploit…
Not rated