# CVE-2017-0073: Information disclosure in Windows GDI+

> Remote attackers can obtain sensitive process memory information via a crafted website, affecting Windows operating systems.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **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:** 17 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-83ph-46mx-g425

## What is CVE-2017-0073?

CVE-2017-0073 is a medium-severity vulnerability in Microsoft Office, published on 17 Mar 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

The Graphics Device Interface (GDI) 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; and Windows 10 Gold, 1511, and 1607 allows remote attackers to obtain sensitive information from process memory via a crafted web site, aka "Windows GDI+ Information Disclosure Vulnerability." This vulnerability is different from those described in CVE-2017-0060 and CVE-2017-0062.

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

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

It affects 14 products.


Products: Microsoft Live Meeting, Microsoft Lync, Microsoft Office, Microsoft Office Word Viewer, Microsoft Skype for Business, Microsoft Skype for Business Basic, 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, Microsoft Windows Vista.

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

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

## Is CVE-2017-0073 being exploited?

There is no known exploitation of CVE-2017-0073 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-0073 and fix it if it is affected.

What it is: CVE-2017-0073 is a medium-severity vulnerability in Microsoft Office, published on 17 Mar 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: There is no known exploitation of CVE-2017-0073 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-0073/ (Markdown: https://insights.sbomify.com/CVE-2017-0073/index.md)
```

## Sources

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

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