# CVE-2017-0038: Information disclosure in Windows Graphics Component

> Remote attackers can obtain sensitive heap memory information via crafted EMF files in Windows GDI, requiring patches to prevent data leakage.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 20 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hv82-656f-m543

## What is CVE-2017-0038?

CVE-2017-0038 is a medium-severity vulnerability in Microsoft Windows 10, published on 20 Feb 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

gdi32.dll in 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 heap memory via a crafted EMF file, as demonstrated by an EMR_SETDIBITSTODEVICE record with modified Device Independent Bitmap (DIB) dimensions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-3216, CVE-2016-3219, and/or CVE-2016-3220.

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

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

It affects 8 products.


Products: 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-0038?

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

## Is CVE-2017-0038 being exploited?

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

Public exploit code:

- https://github.com/k0keoyo/CVE-2017-0038-EXP-C-JS (github_poc): https://github.com/k0keoyo/CVE-2017-0038-EXP-C-JS
- Microsoft Windows - 'gdi32.dll' EMR_SETDIBITSTODEVICE Heap Out-of-Bounds Reads / Memory Disclosure (exploitdb)

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0038 is a medium-severity vulnerability in Microsoft Windows 10, published on 20 Feb 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-0038 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-0038/ (Markdown: https://insights.sbomify.com/CVE-2017-0038/index.md)
```

## Sources

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

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