CVE-2016-5212: Infoleak
Published Jan 19, 2017
·Updated
Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android insufficiently sanitized DevTools URLs, which allowed a remote attacker to read local files via a crafted HTML page.
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-5212?
CVE-2016-5212 is classified as an important vulnerability that could allow unauthorized access to local files.
2
How do I fix CVE-2016-5212?
To fix CVE-2016-5212, update Google Chrome to version 55.0.2883.75 or later.
3
What platforms are affected by CVE-2016-5212?
CVE-2016-5212 affects Google Chrome on Mac, Windows, Linux, and Android platforms.
4
What type of attack does CVE-2016-5212 involve?
CVE-2016-5212 allows a remote attacker to read local files through a specially crafted HTML page.
5
Is CVE-2016-5212 still a threat for current versions of Google Chrome?
No, CVE-2016-5212 is not a threat for current versions of Google Chrome since it has been patched in subsequent releases.