First published: Fri Mar 17 2017(Updated: )
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."
Credit: secure@microsoft.com secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
Microsoft Windows 10 | ||
Microsoft Windows 10 | =1511 | |
Microsoft Windows 10 | =1607 | |
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 8.1 | ||
Microsoft Windows RT | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =r2-sp1 | |
Microsoft Windows Server | ||
Microsoft Windows Server | =r2 | |
Microsoft Windows Server 2016 | ||
Microsoft Windows Vista | =sp2 | |
Microsoft XML Core Services | ||
All of | ||
Microsoft XML Core Services | =3.0 | |
Any of | ||
Microsoft Windows 10 | ||
Microsoft Windows 10 | ||
Microsoft Windows 10 | ||
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 8.1 | ||
Microsoft Windows RT | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =r2-sp1 | |
Microsoft Windows Server | ||
Microsoft Windows Server | =r2 | |
Microsoft Windows Server 2016 | ||
Microsoft Windows Vista | =sp2 | |
Microsoft Windows 8.1 | ||
Microsoft Windows Server | =r2-sp1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-0022 could allow attackers to execute arbitrary code in the context of the current user.
You can check if your system is affected by CVE-2017-0022 by verifying if you are running vulnerable versions of Microsoft XML Core Services on supported Windows versions.
To fix CVE-2017-0022, ensure that you install the latest security updates provided by Microsoft that address this vulnerability.
CVE-2017-0022 affects multiple Windows versions including Windows 7 SP1, Windows 8.1, and various Windows Server editions.
While there is no formal workaround for CVE-2017-0022, best practice is to minimize user privileges and avoid opening untrusted files or links until a patch is applied.