CVE-2016-5182 Memory corruption in Chrome prior to 54.0.2840.59 for Windows, Mac, and Linux; 54.0.2840.85 for Android

High 8.8 Published Updated

Remote attackers can execute arbitrary code via heap corruption in Chrome's bitmap handling by tricking users into visiting crafted HTML pages.

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-5182?

CVE-2016-5182 is a high-severity memory corruption vulnerability in Google Chrome, published on 18 Dec 2016. 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

Blink in Google Chrome prior to 54.0.2840.59 for Windows, Mac, and Linux; 54.0.2840.85 for Android had insufficient validation in bitmap handling, which allowed a remote attacker to potentially exploit heap corruption via crafted HTML pages.

Weakness: CWE-119

Which versions are affected by CVE-2016-5182?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2016-5182?

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-2w74-h4gc-c374, UBUNTU-CVE-2016-5182.

Is CVE-2016-5182 in your software?

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

Check your SBOMs for free