CVE-2017-0022
MediumExploitedPublic exploitMicrosoft 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…
Published Mar 16, 2017 · Updated Apr 22, 2026
Key Facts
Patch immediately- CVE-2017-0022 is a medium-severity vulnerability (CVSS 6.5 v3.1) affecting XML Core Services (Microsoft), Windows 8.1 (Microsoft), Windows Server 2008 (Microsoft) and 1 more product.
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 14, 2017. Public exploit code is available.
- EPSS estimates a 18% probability of exploitation in the next 30 days.
- No fixed version is listed yet; check the vendor advisory for mitigations.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
6.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS (30-day exploit likelihood)
18%
Higher than 97.1% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2017-0022 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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."
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | May 24, 2022 | Jun 14, 2022 | Not reported |
| Industry KEV feed | Mar 14, 2017 | Jun 14, 2022 | Not reported |
| CIRCL KEV | May 24, 2022 | Jun 14, 2022 | Not reported |
| ENISA EUVD | May 24, 2022 | n/a | Not reported |
Required action: Apply updates per vendor instructions.
Affected Products
6 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| XML Core ServicesMicrosoft | 3.0, >= 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 | n/a |
| Windows 8.1Microsoft | See advisory | n/a |
| Windows Server 2008Microsoft | r2-sp1 | n/a |
| Windows Server 2012Microsoft | r2 | n/a |
Timeline
Added to Industry KEV feed
Mar 14, 2017
Publicly disclosed
Mar 16, 2017
Added to CISA KEV
May 24, 2022
Added to CIRCL KEV
May 24, 2022
Added to ENISA EUVD
May 24, 2022
Last updated
Apr 22, 2026
Weakness Type
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
- advisory96069
- advisory1038014
- patchhttps://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0022
- exploithttps://0patch.blogspot.com/2017/09/exploit-kit-rendezvous-and-cve-2017-0022.html
- exploitVulnCheck exploitation report
FAQ
Common Questions.
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 cr…
Affected: XML Core Services (Microsoft) versions 3.0, >= 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; Windows 8.1 (Microsoft); Windows Server 2008 (Microsoft) versions r2-sp1, among others. The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Mar 14, 2017.
Yes. It was added on May 24, 2022 with a federal remediation due date of Jun 14, 2022.
Public exploit code is available.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2017-0022 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo