CVE-2016-5199 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

High 8.8 Published Updated

Remote attackers can exploit heap corruption in FFmpeg via crafted video files to potentially execute 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-5199?

CVE-2016-5199 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

An off by one error resulting in an allocation of zero size in FFmpeg 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 allowed a remote attacker to potentially exploit heap corruption via a crafted video file.

Weakness: CWE-119

Which versions are affected by CVE-2016-5199?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2016-5199?

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

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

All Google Chrome vulnerabilities

Sources

Also known as ALPINE-CVE-2016-5199, DEBIAN-CVE-2016-5199, GHSA-5mc4-xjch-jc3r, UBUNTU-CVE-2016-5199.

Is CVE-2016-5199 in your software?

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

Check your SBOMs for free