Windows Elevation of Privilege Vulnerability
CVE-2017-0050 is fixed in 27 products on 1 platform, first by KB4013198, released March 14, 2017. It is not reported as exploited, but the vendor rates exploitation more likely. Patch Radar priority: Urgent.
<p>An elevation of privilege vulnerability exists in the way that the Windows Kernel API enforces permissions. An attacker who successfully exploited the vulnerability could impersonate processes, interject cross-process communication, or interrupt system functionality.</p> <p>To exploit the vulnerability, a locally authenticated attacker could run a specially crafted application.</p> <p>The security update addresses the vulnerability by helping to ensure that the Windows Kernel API properly enforces permissions.</p>
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Microsoft | |||
| Windows 10 Version 1511 for 32-bit Systems | 10586.839 | KB4013198 | Mar 14, 2017 |
| Windows 10 Version 1511 for x64-based Systems | 10586.839 | KB4013198 | Mar 14, 2017 |
| Windows 10 Version 1607 for 32-bit Systems | 14393.953 | KB4013429 | Mar 14, 2017 |
| Windows 10 Version 1607 for x64-based Systems | 14393.953 | KB4013429 | Mar 14, 2017 |
| Windows 10 for 32-bit Systems | 10240.17319 | KB4012606 | Mar 14, 2017 |
| Windows 10 for x64-based Systems | 10240.17319 | KB4012606 | Mar 14, 2017 |
| Windows 7 for 32-bit Systems Service Pack 1 | KB4012215 | Mar 14, 2017 | |
| Windows 7 for 32-bit Systems Service Pack 1 | KB4012212 | Mar 14, 2017 | |
| Windows 7 for x64-based Systems Service Pack 1 | KB4012215 | Mar 14, 2017 | |
| Windows 7 for x64-based Systems Service Pack 1 | KB4012212 | Mar 14, 2017 | |
| Windows 8.1 for 32-bit systems | KB4012213 | Mar 14, 2017 | |
| Windows 8.1 for 32-bit systems | KB4012216 | Mar 14, 2017 | |
| Windows 8.1 for x64-based systems | KB4012213 | Mar 14, 2017 | |
| Windows 8.1 for x64-based systems | KB4012216 | Mar 14, 2017 | |
| Windows RT 8.1 | KB4012216 | Mar 14, 2017 | |
| Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1 | KB4012215 | Mar 14, 2017 | |
| Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1 | KB4012212 | Mar 14, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | KB4012215 | Mar 14, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 | KB4012212 | Mar 14, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | KB4012215 | Mar 14, 2017 | |
| Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) | KB4012212 | Mar 14, 2017 | |
| Windows Server 2008 for 32-bit Systems Service Pack 2 | KB4011981 | Mar 14, 2017 | |
| Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) | KB4011981 | Mar 14, 2017 | |
| Windows Server 2008 for Itanium-Based Systems Service Pack 2 | KB4011981 | Mar 14, 2017 | |
| Windows Server 2008 for x64-based Systems Service Pack 2 | KB4011981 | Mar 14, 2017 | |
| Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) | KB4011981 | Mar 14, 2017 | |
| Windows Server 2012 | KB4012217 | Mar 14, 2017 | |
| Windows Server 2012 | KB4012214 | Mar 14, 2017 | |
| Windows Server 2012 (Server Core installation) | KB4012217 | Mar 14, 2017 | |
| Windows Server 2012 (Server Core installation) | KB4012214 | Mar 14, 2017 | |
| Windows Server 2012 R2 | KB4012213 | Mar 14, 2017 | |
| Windows Server 2012 R2 | KB4012216 | Mar 14, 2017 | |
| Windows Server 2012 R2 (Server Core installation) | KB4012213 | Mar 14, 2017 | |
| Windows Server 2012 R2 (Server Core installation) | KB4012216 | Mar 14, 2017 | |
| Windows Server 2016 | 14393.953 | KB4013429 | Mar 14, 2017 |
| Windows Server 2016 (Server Core installation) | 14393.953 | KB4013429 | Mar 14, 2017 |
| Windows Vista Service Pack 2 | KB4011981 | Mar 14, 2017 | |
| Windows Vista x64 Edition Service Pack 2 | KB4011981 | Mar 14, 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.