CVE-2016-5210 Memory corruption in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android

High 8.8 Published Updated

A remote attacker can execute arbitrary code via a crafted PDF file exploiting a heap buffer overflow in Chrome's PDFium library.

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

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

Heap buffer overflow during TIFF image parsing in PDFium in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.

Weakness: CWE-787

Which versions are affected by CVE-2016-5210?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2016-5210?

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-6mvw-v46r-jq8g, UBUNTU-CVE-2016-5210.

Is CVE-2016-5210 in your software?

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

Check your SBOMs for free