# CVE-2017-8676: Information disclosure in Windows Graphics Device Interface (GDI)

> An authenticated attacker can retrieve sensitive information from a targeted system via a specially crafted application exploiting the Windows GDI component.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 13 Sep 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-grmq-j248-v2cj

## What is CVE-2017-8676?

CVE-2017-8676 is a low-severity vulnerability in Microsoft Office, published on 13 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Windows Graphics Device Interface (GDI) in 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, 1703, and Server 2016; Office 2007 SP3; Office 2010 SP2; Word Viewer; Office for Mac 2011 and 2016; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; and Live Meeting 2007 Add-in and Console allows an authenticated attacker to retrieve information from a targeted system via a specially crafted application, aka "Windows GDI+ Information Disclosure Vulnerability."

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 14 products.


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

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

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

## Is CVE-2017-8676 being exploited?

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

## Other vulnerabilities in Microsoft Office

- [CVE-2016-7182](https://insights.sbomify.com/CVE-2016-7182/): Code injection in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8676 is a low-severity vulnerability in Microsoft Office, published on 13 Sep 2017. 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-2017-8676 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-2017-8676/ (Markdown: https://insights.sbomify.com/CVE-2017-8676/index.md)
```

## Sources

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

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