CVE-2016-5210: Buffer Overflow
Published 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.
Affected Software
1 affected component
Google Chrome<=54.0.2840.99
Event History
Jan 19, 2017
CVE Published
via MITRE·05:43 AM
Data Sourced
via MITRE·05:43 AM
DescriptionWeakness
Data Sourced
via NVD·05:59 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
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.
2
How do I fix CVE-2016-5210?
To fix CVE-2016-5210, update Google Chrome to version 55.0.2883.75 or later.
3
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.
4
What causes CVE-2016-5210?
CVE-2016-5210 is caused by a heap buffer overflow during TIFF image parsing in PDFium.
5
Can CVE-2016-5210 be exploited remotely?
Yes, a remote attacker can exploit CVE-2016-5210 via a specially crafted PDF file.