Secure Boot Security Feature Bypass Vulnerability
CVE-2016-3287 is fixed in 11 products on 1 platform, first by KB3172985, released July 12, 2016. It is not reported as exploited, but the vendor rates exploitation more likely. Patch Radar priority: Urgent.
<p>A security feature bypass vulnerability exists when Windows Secure Boot improperly applies an affected policy. An attacker who successfully exploited this vulnerability could disable code integrity checks, allowing test-signed executables and drivers to be loaded on a target device. In addition, an attacker could bypass the Secure Boot Integrity Validation for BitLocker and the Device Encryption security features.</p> <p>To exploit the vulnerability, an attacker must either gain administrative privileges or physical access to a target device to install an affected policy.</p> <p>The security update addresses the vulnerability by blacklisting affected policies.</p>
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Microsoft | |||
| Windows 10 Version 1511 for 32-bit Systems | 10586.494 | KB3172985 | Jul 12, 2016 |
| Windows 10 Version 1511 for x64-based Systems | 10586.494 | KB3172985 | Jul 12, 2016 |
| Windows 10 for 32-bit Systems | 10240.17024 | KB3163912 | Jul 12, 2016 |
| Windows 10 for x64-based Systems | 10240.17024 | KB3163912 | Jul 12, 2016 |
| Windows 8.1 for 32-bit systems | KB3172727 | Jul 12, 2016 | |
| Windows 8.1 for x64-based systems | KB3172727 | Jul 12, 2016 | |
| Windows RT 8.1 | KB3172727 | Jul 12, 2016 | |
| Windows Server 2012 | KB3172727 | Jul 12, 2016 | |
| Windows Server 2012 (Server Core installation) | KB3172727 | Jul 12, 2016 | |
| Windows Server 2012 R2 | KB3172727 | Jul 12, 2016 | |
| Windows Server 2012 R2 (Server Core installation) | KB3172727 | Jul 12, 2016 | |
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.