CVE-2017-15392
UnknownEPSS 0.84%
Last modified
CVE-2017-15392 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.84% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 62.0.3202.62 | |
| Debian | Debian Linux | 8.0 |
| Debian | Debian Linux | 9.0 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is 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 potentially exploit heap corruption via a crafted Windows Registry entry, related to PlatformIntegration.
How severe is CVE-2017-15392?
Severity scoring for CVE-2017-15392 is pending analysis. The EPSS model estimates a 0.84% probability of exploitation in the next 30 days.
How do I fix CVE-2017-15392?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-15387Insufficient enforcement of Content Security Policy in Blink…
- CVE-2017-15388Iteration through non-finite points in Skia in Google Chrome…
- CVE-2017-15389An insufficient watchdog timer in navigation in Google Chrom…
- CVE-2017-1539IBM Business Process Manager 7.5, 8.0, and 8.5 is vulnerable…
- CVE-2017-15390Insufficient Policy Enforcement in Omnibox in Google Chrome …
- CVE-2017-15391Insufficient Policy Enforcement in Extensions in Google Chro…
- CVE-2017-15393Insufficient Policy Enforcement in Devtools remote debugging…
- CVE-2017-15394Insufficient Policy Enforcement in Extensions in Google Chro…
- CVE-2017-15395A use after free in Blink in Google Chrome prior to 62.0.320…
- CVE-2017-15396A stack buffer overflow in NumberingSystem in International …
- CVE-2017-15397Inappropriate implementation in ChromeVox in Google Chrome O…
- CVE-2017-15398A stack buffer overflow in the QUIC networking stack in Goog…
Are you affected by CVE-2017-15392?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST