CVE-2017-0022
Microsoft XML Core Services Information Disclosure Vulnerability
Microsoft XML Core Services
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."
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 24 May 2022. US federal agencies were required to remediate it by 14 June 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 18.1%, which is higher than 97.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2017-0022 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2017-0022.
What does CVE-2017-0022 affect?
CVE-2017-0022 affects Microsoft XML Core Services. 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."
How severe is CVE-2017-0022?
CVE-2017-0022 is rated MEDIUM with a CVSS base score of 6.5. EPSS puts the probability of exploitation in the next 30 days at 18.1%, higher than 97.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 14 June 2022.
How should organisations respond to CVE-2017-0022?
Apply the vendor patch for Microsoft XML Core Services as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.