CVE-2017-0216

Device Guard Code Integrity Policy Security Feature Bypass Vulnerability

CVE-2017-0216 is fixed in 6 products on 1 platform, first by KB4022714, released June 13, 2017. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.3
Important
Exploitation
None reported
Exploitation Less Likely
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0145
73rd percentile

<p>A security feature bypass vulnerability exists in Device Guard that could allow an attacker to inject malicious code into a Windows PowerShell session. An attacker who successfully exploited this vulnerability could inject code into a trusted PowerShell process to bypass the Device Guard Code Integrity policy on the local machine.</p> <p>To exploit the vulnerability, an attacker would first have to access the local machine, and then inject malicious code into a script that is trusted by the Code Integrity policy. The injected code would then run with the same trust level as the script and bypass the Code Integrity policy.</p> <p>The update addresses the vulnerability by correcting how PowerShell exposes functions and processes user supplied code.</p>

Where it's fixed

ProductFixed inFixReleased
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 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.