CVE-2017-5036: Use After Free
Published Apr 24, 2017
·Updated
A use after free in PDFium in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android allowed a remote attacker to have an unspecified impact via a crafted PDF file.
Affected Software
17 affected components
Google Chrome<=57.0.2987.75
Apple macOS
Linux Linux kernel
Microsoft Windows
Google Chrome<=57.0.2987.100
Google Android
Debian Debian Linux=8.0
Debian Debian Linux=9.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
All of the following
Google Chrome<=57.0.2987.75
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
All of the following
Google Chrome<=57.0.2987.100
Google Android
Remediation
Patch Available
Event History
Apr 24, 2017
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
DescriptionWeakness
Data Sourced
via NVD·11:59 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2017-5036?
CVE-2017-5036 is rated as a high severity vulnerability due to its potential to allow remote code execution via crafted PDF files.
2
How do I fix CVE-2017-5036?
To address CVE-2017-5036, update Google Chrome to the latest version beyond 57.0.2987.98.
3
What platforms are affected by CVE-2017-5036?
CVE-2017-5036 affects Google Chrome on Mac, Windows, and Linux operating systems.
4
Can CVE-2017-5036 be exploited remotely?
Yes, a remote attacker can exploit CVE-2017-5036 by delivering a crafted PDF file to the affected Chrome version.
5
Is this vulnerability specific to certain Chrome versions?
CVE-2017-5036 specifically affects versions of Google Chrome up to and including 57.0.2987.98.