CVE-2017-5032 Memory corruption in Google Chrome prior to 57.0.2987.98 for Windows

High 8.8 Published Updated

Remote attackers can execute arbitrary code via heap corruption in PDFium by tricking users into opening a crafted PDF file 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-2017-5032?

CVE-2017-5032 is a high-severity memory corruption vulnerability in Google Chrome, published on 24 Apr 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

PDFium in Google Chrome prior to 57.0.2987.98 for Windows could be made to increment off the end of a buffer, which allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.

Weakness: CWE-787

Which versions are affected by CVE-2017-5032?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2017-5032?

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

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

All Google Chrome vulnerabilities

Sources

Also known as GHSA-vmp4-486w-93fw, UBUNTU-CVE-2017-5032.

Is CVE-2017-5032 in your software?

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

Check your SBOMs for free