Windows Remote Code Execution Vulnerability
CVE-2017-0294 is fixed in 27 products on 1 platform, first by KB4022714, released June 13, 2017. It is not reported as exploited. Patch Radar priority: Urgent.
<p>A remote code execution vulnerability exists when Microsoft Windows fails to properly handle cabinet files.</p> <p>To exploit the vulnerability, an attacker would have to convince a user to either open a specially crafted cabinet file or spoof a network printer and trick a user into installing a malicious cabinet file disguised as a printer driver.</p> <p>The update addresses the vulnerability by correcting how Windows handles cabinet files.</p>
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Microsoft | |||
| Windows 10 Version 1511 for 32-bit Systems | 10586.962 | KB4022714 | Jun 13, 2017 |
| Windows 10 Version 1511 for x64-based Systems | 10586.962 | KB4022714 | Jun 13, 2017 |
| Windows 10 Version 1607 for 32-bit Systems | 14393.1358 | KB4022715 | Jun 13, 2017 |
| Windows 10 Version 1607 for x64-based Systems | 14393.1358 | KB4022715 | Jun 13, 2017 |
| Windows 10 Version 1703 for 32-bit Systems | KB4022725 | Jun 13, 2017 | |
| Windows 10 Version 1703 for x64-based Systems | KB4022725 | Jun 13, 2017 | |
| Windows 10 for 32-bit Systems | 10240.17443 | KB4022727 | Jun 13, 2017 |
| Windows 10 for x64-based Systems | 10240.17443 | KB4022727 | Jun 13, 2017 |
| Windows 7 for 32-bit Systems Service Pack 1 | KB4022719 | Jun 13, 2017 | |
| Windows 7 for 32-bit Systems Service Pack 1 | KB4022722 | Jun 13, 2017 | |
| Windows 7 for x64-based Systems Service Pack 1 | KB4022719 | Jun 13, 2017 | |
| Windows 7 for x64-based Systems Service Pack 1 | KB4022722 | Jun 13, 2017 | |
| Windows 8.1 for 32-bit systems | KB4022717 | Jun 13, 2017 | |
| Windows 8.1 for 32-bit systems | KB4022726 | Jun 13, 2017 | |
| Windows 8.1 for x64-based systems | KB4022717 | Jun 13, 2017 | |
| Windows 8.1 for x64-based systems | KB4022726 | Jun 13, 2017 | |
| Windows RT 8.1 | KB4022726 | Jun 13, 2017 | |
| Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1 | KB4022719 | Jun 13, 2017 | |
| Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1 | KB4022722 | Jun 13, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | KB4022719 | Jun 13, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | KB4022722 | Jun 13, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | KB4022719 | Jun 13, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | KB4022722 | Jun 13, 2017 | |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | KB4022008 | Jun 13, 2017 | |
| Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) | KB4022008 | Jun 13, 2017 | |
| Windows Server 2008 for Itanium-Based Systems Service Pack 2 | KB4022008 | Jun 13, 2017 | |
| Windows Server 2008 for x64-based Systems Service Pack 2 | KB4022008 | Jun 13, 2017 | |
| Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) | KB4022008 | Jun 13, 2017 | |
| Windows Server 2012 | KB4022724 | Jun 13, 2017 | |
| Windows Server 2012 | KB4022718 | Jun 13, 2017 | |
| Windows Server 2012 (Server Core installation) | KB4022724 | Jun 13, 2017 | |
| Windows Server 2012 (Server Core installation) | KB4022718 | Jun 13, 2017 | |
| Windows Server 2012 R2 | KB4022717 | Jun 13, 2017 | |
| Windows Server 2012 R2 | KB4022726 | Jun 13, 2017 | |
| Windows Server 2012 R2 (Server Core installation) | KB4022717 | Jun 13, 2017 | |
| Windows Server 2012 R2 (Server Core installation) | KB4022726 | Jun 13, 2017 | |
| Windows Server 2016 | 14393.1358 | KB4022715 | Jun 13, 2017 |
| Windows Server 2016 (Server Core installation) | 14393.1358 | KB4022715 | Jun 13, 2017 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.