CVE-2017-5133 Memory corruption in Google Chrome prior to 62.0.3202.62

High 8.8 Published Updated

Remote attackers can execute code or leak information via crafted PDF files due to heap memory corruption in Chrome's Blink engine.

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

CVE-2017-5133 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 7 Feb 2018. 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

Off-by-one read/write on the heap in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to corrupt memory and possibly leak information and potentially execute code via a crafted PDF file.

Weakness: CWE-787

Which versions are affected by CVE-2017-5133?

It affects 2 products.

Products include Debian Debian Linux, Google Chrome.

How do I fix CVE-2017-5133?

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

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

All Debian Debian Linux vulnerabilities

Sources

Also known as GHSA-rxvj-92w6-px48, UBUNTU-CVE-2017-5133.

Is CVE-2017-5133 in your software?

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

Check your SBOMs for free