# CVE-2017-8682: Memory corruption in Windows graphics

> Attackers can execute remote code via malicious embedded fonts in Windows graphics components, affecting multiple Windows and Office versions.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Sep 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h72p-r49x-6h8h

## What is CVE-2017-8682?

CVE-2017-8682 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 13 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Windows graphics on Microsoft 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, 1607, and 1703, Windows Server 2016, Microsoft Office Word Viewer, Microsoft Office 2007 Service Pack 3 , and Microsoft Office 2010 Service Pack 2 allows an attacker to execute remote code by the way it handles embedded fonts, aka "Win32k Graphics Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8683.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-8682?

It affects 10 products.


Products: Microsoft Office 2007, Microsoft Office 2010, Microsoft Office Word Viewer, 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 Server 2016.

## How do I fix CVE-2017-8682?

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

## Is CVE-2017-8682 being exploited?

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

Public exploit code:

- Microsoft Windows Kernel - 'win32k.sys' '.TTF' Font Processing Out-of-Bounds Reads/Writes with Malformed 'fpgm' table 'win32k!bGeneratePath' (Denial of Service) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8682 and fix it if it is affected.

What it is: CVE-2017-8682 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 13 Sep 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8682 exists.

Affected product: Microsoft Windows 10. 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-2017-8682/ (Markdown: https://insights.sbomify.com/CVE-2017-8682/index.md)
```

## Sources

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

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