# CVE-2017-0108: Memory corruption in Windows Graphics Component

> Remote attackers can execute arbitrary code via a crafted website exploiting a memory corruption flaw in the Windows Graphics Component.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qp4j-h89h-v85j

## What is CVE-2017-0108?

CVE-2017-0108 is a high-severity memory corruption vulnerability in Microsoft Office, published on 17 Mar 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Windows Graphics Component in Microsoft Office 2007 SP3; 2010 SP2; and Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Live Meeting 2007; Silverlight 5; Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; and Windows 7 SP1 allows remote attackers to execute arbitrary code via a crafted web site, aka "Graphics Component Remote Code Execution Vulnerability." This vulnerability is different from that described in CVE-2017-0014.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 9 products.


Products: Microsoft Live Meeting, Microsoft Lync, Microsoft Office, Microsoft Silverlight, Microsoft Skype for Business, Microsoft Windows 7, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Word Viewer.

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

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

## Is CVE-2017-0108 being exploited?

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

Public exploit code:

- https://github.com/homjxi0e/CVE-2017-0108 (github_poc): https://github.com/homjxi0e/CVE-2017-0108
- Microsoft Windows - 'USP10!otlList::insertAt' Uniscribe Font Processing Heap Buffer Overflow (MS17-011) (exploitdb)

## 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-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-2017-0108 and fix it if it is affected.

What it is: CVE-2017-0108 is a high-severity memory corruption vulnerability in Microsoft Office, published on 17 Mar 2017. It can only be exploited from the same machine or local network, 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-0108 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-2017-0108/ (Markdown: https://insights.sbomify.com/CVE-2017-0108/index.md)
```

## Sources

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

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