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

Medium 5.3 Published Updated

A remote attacker can perform an out-of-bounds memory read via crafted PDF files due to incorrect object handling in Chrome DevTools after a tab crash.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2016-5186?

CVE-2016-5186 is a medium-severity memory corruption vulnerability in Google Chrome, published on 18 Dec 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

Devtools in Google Chrome prior to 54.0.2840.59 for Windows, Mac, and Linux; 54.0.2840.85 for Android incorrectly handled objects after a tab crash, which allowed a remote attacker to perform an out of bounds memory read via crafted PDF files.

Weakness: CWE-125

Which versions are affected by CVE-2016-5186?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2016-5186?

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-3gjx-83h4-mg3w, UBUNTU-CVE-2016-5186.

Is CVE-2016-5186 in your software?

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

Check your SBOMs for free