Vulnerabilities · 2017 · Google
CVE-2017-15392
Google Chrome vulnerability
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
Chrome, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.securityfocus.com/bid/101482
- access.redhat.com/errata/RHSA-2017:2997
- chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html
- crbug.com/714401
- security.gentoo.org/glsa/201710-24
- www.debian.org/security/2017/dsa-4020
- nvd.nist.gov/vuln/detail/CVE-2017-15392
- cve.org/CVERecord?id=CVE-2017-15392
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.