# CVE-2016-0057: Security feature bypass in n/a

> Local attackers can gain privileges by exploiting improper binary signing in Microsoft Office via a Trojan horse file.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xr6x-5h2r-x4p8

## What is CVE-2016-0057?

CVE-2016-0057 is a high-severity vulnerability in Microsoft Office, published on 9 Mar 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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."

Weakness: CWE-264

## Which versions are affected by CVE-2016-0057?

It affects 1 product.


Products: Microsoft Office.

## How do I fix CVE-2016-0057?

No fix has been published for CVE-2016-0057 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-0057 being exploited?

There is no known exploitation of CVE-2016-0057 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0057 and fix it if it is affected.

What it is: CVE-2016-0057 is a high-severity vulnerability in Microsoft Office, published on 9 Mar 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-0057 in the wild and no public exploit code.

Affected product: Microsoft Office. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-0057/ (Markdown: https://insights.sbomify.com/CVE-2016-0057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-0057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-0057
- OSV: https://osv.dev/vulnerability/CVE-2016-0057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-0057/
Summaries are generated and may contain mistakes; the official description above is the record.