CVE-2016-5214
First published: Thu Jan 19 2017(Updated: )
Google Chrome prior to 55.0.2883.75 for Windows mishandled downloaded files, which allowed a remote attacker to prevent the downloaded file from receiving the Mark of the Web 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 |
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-2016-5214?
CVE-2016-5214 has a medium severity rating, which indicates a potential risk to users of affected Google Chrome versions.
How do I fix CVE-2016-5214?
To fix CVE-2016-5214, you should update Google Chrome to version 55.0.2883.75 or later.
What are the consequences of CVE-2016-5214?
CVE-2016-5214 allows a remote attacker to prevent the Mark of the Web from being applied to downloaded files, which can lead to security issues.
Which versions of Google Chrome are affected by CVE-2016-5214?
CVE-2016-5214 affects Google Chrome versions prior to 55.0.2883.75 on Windows.
Is there a workaround for CVE-2016-5214?
There are no specific workarounds for CVE-2016-5214 other than upgrading to the latest version of Google Chrome.
- agent/type
- agent/severity
- agent/weakness
- agent/remedy
- 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