CVE-2017-5032: Buffer Overflow
First published: Mon 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.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome | <=57.0.2987.75 | |
| Microsoft Windows Operating System |
Remedy
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
How do I fix CVE-2017-5032?
To fix CVE-2017-5032, update Google Chrome to version 57.0.2987.98 or later.
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.
What versions of Google Chrome are affected by CVE-2017-5032?
CVE-2017-5032 affects Google Chrome versions before 57.0.2987.98.
Is CVE-2017-5032 specific to any operating system?
CVE-2017-5032 specifically targets Google Chrome for Windows.
- agent/references
- agent/type
- agent/severity
- agent/remedy
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/event
- agent/first-publish-date
- agent/trending
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome
- version/google chrome/57.0.2987.75
- vendor/microsoft
- canonical/microsoft windows operating system