CVE-2017-5032: Buffer Overflow
Published Apr 24, 2017
·Updated
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.
Affected Software
4 affected components
Google Chrome<=57.0.2987.75
Microsoft Windows
All of the following
Google Chrome<=57.0.2987.75
Microsoft Windows
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-5032?
CVE-2017-5032 is classified as a critical vulnerability due to its potential for heap corruption and remote exploitation.
2
How do I fix CVE-2017-5032?
To fix CVE-2017-5032, update Google Chrome to version 57.0.2987.98 or later.
3
What can attackers do with CVE-2017-5032?
Attackers could exploit CVE-2017-5032 by crafting a malicious PDF file that leads to heap corruption.
4
What versions of Google Chrome are affected by CVE-2017-5032?
CVE-2017-5032 affects Google Chrome versions before 57.0.2987.98.
5
Is CVE-2017-5032 specific to any operating system?
CVE-2017-5032 specifically targets Google Chrome for Windows.