CVE-2017-15392 Memory corruption in Google Chrome prior to 62.0.3202.62
An attacker with Windows Registry write access can exploit heap corruption in Chrome's V8 engine to potentially execute arbitrary code.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-15392?
CVE-2017-15392 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 7 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-20
Which versions are affected by CVE-2017-15392?
It affects 2 products.
Products include Debian Debian Linux, Google Chrome.
How do I fix CVE-2017-15392?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-15392 being exploited?
There is no known exploitation of CVE-2017-15392 in the wild and no public exploit code.
Other vulnerabilities in Debian Debian Linux
Sources
Also known as GHSA-vv4q-vxg5-8gfj, UBUNTU-CVE-2017-15392.