VDB

CVE-2017-15392

CVE-2017-15392 PUBLISHED

Reported by chrome · Published February 7, 2018

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromegoogle62.0.3202.62
chromium-browserUbuntu:14.04:LTS62.0.3202.62-0ubuntu0.14.04.1204
chromium-browserUbuntu:18.04:LTS62.0.3202.62-0ubuntu0.17.10.1380

Affected products

VendorProductVersions
n/aGoogle Chrome prior to 62.0.3202.62Google Chrome prior to 62.0.3202.62
n/aGoogle Chrome prior to 62.0.3202.6262.0.3202.62
archchromium0

Timeline

  • Oct 18, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Jun 2, 2026 Security Advisory (5 in total, the first dated here)
  • Aug 9, 2026 Distribution Patch (2 in total, the first dated here)
  • Oct 2, 2026 Coalition ESS Score
  • Oct 18, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-15392
vulnetix vdb fixes CVE-2017-15392

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-15392/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›