CVE-2016-5212: Infoleak
First published: Thu 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.
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-5212?
CVE-2016-5212 is classified as an important vulnerability that could allow unauthorized access to local files.
How do I fix CVE-2016-5212?
To fix CVE-2016-5212, update Google Chrome to version 55.0.2883.75 or later.
What platforms are affected by CVE-2016-5212?
CVE-2016-5212 affects Google Chrome on Mac, Windows, Linux, and Android platforms.
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.
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.
- agent/type
- agent/severity
- agent/weakness
- agent/references
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/first-publish-date
- agent/trending
- collector/nvd-index
- agent/software-canonical-lookup-request
- 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