CVE-2016-5200 Memory corruption in Google Chrome prior to 54.0.2840.98 for Mac, and 54.0.2840.99 for Windows, and 54.0.2840.100 for Linux, and 55.0.2883.84 for Android
Remote attackers can exploit heap corruption in V8 via crafted HTML pages, potentially executing arbitrary code in Google Chrome.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2016-5200?
CVE-2016-5200 is a high-severity memory corruption vulnerability in Google Chrome, published on 19 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
V8 in Google Chrome prior to 54.0.2840.98 for Mac, and 54.0.2840.99 for Windows, and 54.0.2840.100 for Linux, and 55.0.2883.84 for Android incorrectly applied type rules, which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Weakness: CWE-119
Which versions are affected by CVE-2016-5200?
It affects 1 product.
Products include Google Chrome.
How do I fix CVE-2016-5200?
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-2016-5200 being exploited?
There is no known exploitation of CVE-2016-5200 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-hjwp-q5hc-9xxq, UBUNTU-CVE-2016-5200.