LiveActive security incident?Get immediate response
CVE Record

CVE-2017-15392: Insufficient data validation in V8 in Google Chrome prior to 62.0.3202.62 allowed an attacker who can write...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is an old Google Chrome V8 flaw affecting versions before 62.0.3202.62. An attacker who can already write to the Windows Registry could trigger heap corruption through a crafted registry entry. Business risk is mainly legacy or unmanaged endpoints still running very old Chrome builds.

Executive priority

Medium priority unless legacy Chrome is still present. This should be handled through endpoint hygiene and browser lifecycle management, not emergency incident response, because the bundle does not show active exploitation and the affected version is very old.

Technical view

CVE-2017-15392 is insufficient data validation in Chrome V8, related to PlatformIntegration. The public description ties exploitation to an attacker able to write a crafted Windows Registry entry, with potential heap corruption. The bundle provides no CVSS score, CWE, exploit details, or confirmed active exploitation.

Likely exposure

Exposure is likely limited to systems running Google Chrome before 62.0.3202.62, especially Windows endpoints where an attacker or malicious local process can modify relevant Registry data. Current managed Chrome fleets should have low exposure if update controls are working.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The attacker prerequisite is meaningful: registry write capability is required before the heap corruption condition becomes reachable, based on the CVE description.

Researcher notes

The key research constraint is the Registry write prerequisite. The public bundle does not provide scoring, root-cause detail beyond V8 PlatformIntegration, or proof of exploitation. Avoid assuming remote drive-by reachability without additional vendor evidence.

Mitigation direction

  • Upgrade Google Chrome to 62.0.3202.62 or later.
  • Apply relevant Debian, Red Hat, or Gentoo security updates where Chromium packages are managed by the OS.
  • Check current vendor guidance for any platform-specific remediation notes.
  • Treat unsupported legacy browser installations as remediation priorities.
  • Restrict unnecessary Registry write access on Windows endpoints as defense in depth.

Validation and detection

  • Inventory Chrome versions and flag anything before 62.0.3202.62.
  • Confirm managed update policy enforces current Chrome or Chromium builds.
  • Review Windows endpoints for legacy Chrome installations outside standard management.
  • Check Linux package status against the cited Debian, Red Hat, and Gentoo advisories.
  • Document exceptions where old browser versions remain business-required.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-15392 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aGoogle Chrome prior to 62.0.3202.62Google Chrome prior to 62.0.3202.62Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.