# CVE-2017-0170: XML external entity in 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 Windows Server 2016

> An attacker can exploit an XML parsing flaw in Windows Performance Monitor to disclose sensitive information.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:** 11 Jul 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6j2g-pgmq-rm4f

## What is CVE-2017-0170?

CVE-2017-0170 is a medium-severity vulnerability in Microsoft Windows 10, published on 11 Jul 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 Performance Monitor in 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 Windows Server 2016 allows an information disclosure vulnerability due to the way it parses XML input, aka "Windows Performance Monitor Information Disclosure Vulnerability".

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 6 products.


Products: Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

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

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

## Is CVE-2017-0170 being exploited?

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

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

What it is: CVE-2017-0170 is a medium-severity vulnerability in Microsoft Windows 10, published on 11 Jul 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-0170 in the wild and no public exploit code.

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-0170/ (Markdown: https://insights.sbomify.com/CVE-2017-0170/index.md)
```

## Sources

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

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