Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

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 Windows Registry to…

Medium4.3EPSS 0.79%
Published
Updated
Reserved
Assigned by
Chrome

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.

Scores

CVSS scores of CVE-2017-15392, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.0Medium4.3CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS (exploitation in 30 days)
0.79% · top 43% of all CVEs (5 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.3.

Weakness

Affected products

  • Google Chrome prior to 62.0.3202.62

    • affected Google Chrome prior to 62.0.3202.62

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2017-15392 badge
[![CVE-2017-15392](https://trackcve.app/badge/CVE-2017-15392.svg)](https://trackcve.app/cve/CVE-2017-15392)

Record last updated .