CVE-2016-0057
First published: Wed Mar 09 2016(Updated: )
Microsoft Office 2007 SP3, 2010 SP2, 2013 SP1, and 2016 does not properly sign an unspecified binary file, which allows local users to gain privileges via a Trojan horse file with a crafted signature, aka "Microsoft Office Security Feature Bypass Vulnerability."
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Office | =2007-sp3 | |
| Microsoft Office | =2010-sp2 | |
| Microsoft Office | =2013-sp1 | |
| Microsoft Office | =2016 |
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-0057?
CVE-2016-0057 has a high severity rating due to its potential to allow privilege escalation through an improperly signed binary.
How do I fix CVE-2016-0057?
To mitigate CVE-2016-0057, users should apply the latest security updates provided by Microsoft for Office 2007, 2010, 2013, and 2016.
Who is affected by CVE-2016-0057?
CVE-2016-0057 affects users of Microsoft Office 2007 SP3, 2010 SP2, 2013 SP1, and 2016 versions.
What type of attack is possible with CVE-2016-0057?
CVE-2016-0057 allows a local user to gain elevated privileges by executing a Trojan horse file with a crafted signature.
When was CVE-2016-0057 disclosed?
CVE-2016-0057 was disclosed by Microsoft in March 2016 as part of their security bulletin.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/severity
- agent/author
- agent/weakness
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/microsoft office
- version/microsoft office/2007-sp3
- version/microsoft office/2010-sp2
- version/microsoft office/2013-sp1
- version/microsoft office/2016