CVE-2016-5210: Buffer Overflow
First published: Thu Jan 19 2017(Updated: )
Heap buffer overflow during TIFF image parsing in PDFium in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.
Credit: cve-coordination@google.com chrome-cve-admin@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <=54.0.2840.99 | |
| Google Chrome | <=54.0.2840.99 |
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-2016-5210?
CVE-2016-5210 is classified as a high severity vulnerability due to the potential for remote exploitation.
How do I fix CVE-2016-5210?
To fix CVE-2016-5210, update Google Chrome to version 55.0.2883.75 or later.
What types of systems are affected by CVE-2016-5210?
CVE-2016-5210 affects Google Chrome versions prior to 55.0.2883.75 on Mac, Windows, and Linux, as well as 55.0.2883.84 on Android.
What causes CVE-2016-5210?
CVE-2016-5210 is caused by a heap buffer overflow during TIFF image parsing in PDFium.
Can CVE-2016-5210 be exploited remotely?
Yes, a remote attacker can exploit CVE-2016-5210 via a specially crafted PDF file.
- agent/type
- agent/severity
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/first-publish-date
- agent/trending
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/weakness
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/author
- agent/last-modified-date
- agent/softwarecombine
- agent/source
- agent/tags
- agent/event
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/54.0.2840.99
- canonical/google chrome
- version/google chrome/54.0.2840.99