CVE-2017-5057 Memory corruption in Google Chrome prior to 58.0.3029.81 for Mac, Windows and Linux, and 58.0.3029.83 for Android
A remote attacker can perform an out-of-bounds memory read via a crafted PDF file in Google Chrome, potentially exposing sensitive information.
- 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-5057?
CVE-2017-5057 is a high-severity memory corruption vulnerability in Google Chrome, published on 27 Oct 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
Type confusion in PDFium in Google Chrome prior to 58.0.3029.81 for Mac, Windows, and Linux, and 58.0.3029.83 for Android, allowed a remote attacker to perform an out of bounds memory read via a crafted PDF file.
Weakness: CWE-843
Which versions are affected by CVE-2017-5057?
It affects 4 products.
Products include Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.
How do I fix CVE-2017-5057?
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-5057 being exploited?
There is no known exploitation of CVE-2017-5057 in the wild and no public exploit code.
Other vulnerabilities in Google Chrome
Sources
Also known as GHSA-r367-gwgr-rxq8, UBUNTU-CVE-2017-5057.