# CVE-2016-7182: Code injection in n/a

> Attackers can execute arbitrary code and escalate privileges by exploiting a flaw in the Windows Graphics component via a crafted TrueType font.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h83x-2g4x-q692

## What is CVE-2016-7182?

CVE-2016-7182 is a critical code injection vulnerability in Microsoft Office, published on 14 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Graphics component in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold, 1511, and 1607; Office 2007 SP3; Office 2010 SP2; Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; and Live Meeting 2007 Console allows attackers to execute arbitrary code via a crafted True Type font, aka "True Type Font Parsing Elevation of Privilege Vulnerability."

Weakness: CWE-20 (Improper Input Validation)

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

It affects 12 products.


Products: Microsoft Live Meeting, Microsoft Lync, Microsoft Office, Microsoft Skype for Business, Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Word Viewer.

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

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

## Is CVE-2016-7182 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-7182 exists.

Public exploit code:

- Microsoft Windows - 'win32k.sys' TTF Processing win32k!sbit_Embolden / win32k!ttfdCloseFontContext Use-After-Free (MS16-120) (exploitdb)

## Other vulnerabilities in Microsoft Office

- [CVE-2015-6106](https://insights.sbomify.com/CVE-2015-6106/): Memory corruption in n/a (critical 9.3)
- [CVE-2015-6107](https://insights.sbomify.com/CVE-2015-6107/): Memory corruption in n/a (critical 9.3)
- [CVE-2015-2431](https://insights.sbomify.com/CVE-2015-2431/): Code injection in n/a (critical 9.3)
- [CVE-2017-0108](https://insights.sbomify.com/CVE-2017-0108/): Memory corruption in Windows Graphics Component (high 7.8)
- [CVE-2016-3396](https://insights.sbomify.com/CVE-2016-3396/): Code injection in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-7182 is a critical code injection vulnerability in Microsoft Office, published on 14 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-7182 exists.

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-7182/ (Markdown: https://insights.sbomify.com/CVE-2016-7182/index.md)
```

## Sources

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

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