CVE-2017-5039: 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 potentially exploit heap corruption 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-5039?
CVE-2017-5039 has a high severity due to its potential to enable remote attackers to exploit heap corruption.
2
How do I fix CVE-2017-5039?
To fix CVE-2017-5039, upgrade Google Chrome to version 57.0.2987.98 or later.
3
Which versions of Google Chrome are affected by CVE-2017-5039?
CVE-2017-5039 affects Google Chrome versions up to and including 57.0.2987.75.
4
Can CVE-2017-5039 affect Mac users?
Yes, CVE-2017-5039 can affect Mac users who have an affected version of Google Chrome installed.
5
What platforms are impacted by CVE-2017-5039?
CVE-2017-5039 impacts Google Chrome on Mac, Windows, Linux, and some older versions of Android.