# CVE-2017-0022: Microsoft XML Core Services Information Disclosure

> Attackers can determine file existence on disk via crafted websites due to improper memory handling in Microsoft XML Core Services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 24 May 2022 (CISA KEV)
- **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:** 21 Oct 2025
- **Also known as:** GHSA-r6m8-274g-vhp5

## What is CVE-2017-0022?

CVE-2017-0022 is a medium-severity vulnerability in Microsoft Windows 8.1, 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

Microsoft XML Core Services (MSXML) in Windows 10 Gold, 1511, and 1607; Windows 7 SP1; Windows 8.1; Windows RT 8.1; Windows Server 2008 SP2 and R2 SP1; Windows Server 2012 Gold and R2; Windows Server 2016; and Windows Vista SP2 improperly handles objects in memory, allowing attackers to test for files on disk via a crafted web site, aka "Microsoft XML Information Disclosure Vulnerability."

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

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

It affects 4 products.


Products: Microsoft Windows 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Xml Core Services.

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

No fix has been published for CVE-2017-0022 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Jun 2022.

## Is CVE-2017-0022 being exploited?

Yes. Attackers have exploited CVE-2017-0022 in the wild since at least 24 May 2022.

## Other vulnerabilities in Microsoft Windows 8.1

- [CVE-2016-3300](https://insights.sbomify.com/CVE-2016-3300/): Privilege escalation in n/a (high 7.8)
- [CVE-2016-0044](https://insights.sbomify.com/CVE-2016-0044/): Denial of service in n/a (high 7.5)
- [CVE-2015-2361](https://insights.sbomify.com/CVE-2015-2361/): Memory corruption in n/a (high 7.2)
- [CVE-2015-0058](https://insights.sbomify.com/CVE-2015-0058/): Double free vulnerability in win32k.sys in the kernel-mode drivers in Microsoft Windows 8.1, Windows Server 2012 R2, and Windows RT 8.1 allo (high 7.2)
- [CVE-2017-0168](https://insights.sbomify.com/CVE-2017-0168/): Information disclosure in Windows Hyper-V (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0022 is a medium-severity vulnerability in Microsoft Windows 8.1, 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: Yes. Attackers have exploited CVE-2017-0022 in the wild since at least 24 May 2022.

Affected product: Microsoft Windows 8.1. 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-0022/ (Markdown: https://insights.sbomify.com/CVE-2017-0022/index.md)
```

## Sources

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

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