CVE-2016-3320

Secure Boot Security Feature Bypass Vulnerability

CVE-2016-3320 is fixed in 11 products on 1 platform, first by KB3172729, released August 9, 2016. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
6.6
Important
Exploitation
None reported
Exploitation Less Likely
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0487
92nd percentile

<p>A security feature bypass vulnerability exists when Windows Secure Boot improperly loads a boot manager that is affected by the vulnerability. An attacker who successfully exploited this vulnerability could disable code integrity checks, allowing test-signed executables and drivers to be loaded onto a target device. Furthermore, the attacker could bypass Secure Boot Integrity Validation for BitLocker and Device Encryption security features.</p> <p>To exploit the vulnerability, an attacker who has gained administrative privileges or who has physical access to a target device could install an affected boot manager and then install a policy affected by the vulnerability onto a target device.</p> <p>The security update addresses the vulnerability by blacklisting affected boot managers.</p>

Where it's fixed

ProductFixed inFixReleased
Microsoft
Windows 10 Version 1511 for 32-bit Systems KB3172729 Aug 9, 2016
Windows 10 Version 1511 for x64-based Systems KB3172729 Aug 9, 2016
Windows 10 for 32-bit Systems KB3172729 Aug 9, 2016
Windows 10 for x64-based Systems KB3172729 Aug 9, 2016
Windows 8.1 for 32-bit systems KB3172729 Aug 9, 2016
Windows 8.1 for x64-based systems KB3172729 Aug 9, 2016
Windows RT 8.1 KB3172729 Aug 9, 2016
Windows Server 2012 KB3172729 Aug 9, 2016
Windows Server 2012 (Server Core installation) KB3172729 Aug 9, 2016
Windows Server 2012 R2 KB3172729 Aug 9, 2016
Windows Server 2012 R2 (Server Core installation) KB3172729 Aug 9, 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.