CVE-2017-5012 Memory corruption in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android

High 8.8 Published Updated

A remote attacker can execute arbitrary code via a crafted HTML page exploiting a heap buffer overflow in the V8 engine.

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-2017-5012?

CVE-2017-5012 is a high-severity memory corruption vulnerability in Google Chrome, published on 17 Feb 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

A heap buffer overflow in V8 in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Weakness: CWE-119

Which versions are affected by CVE-2017-5012?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2017-5012?

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-5012 being exploited?

There is no known exploitation of CVE-2017-5012 in the wild and no public exploit code.

All Google Chrome vulnerabilities

Sources

Also known as GHSA-6w86-823g-r25g, UBUNTU-CVE-2017-5012.

Is CVE-2017-5012 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free