Security Update for Secure Boot (3179577)Published: August 9, 2016Version: 1.0This security update resolves a vulnerability in Microsoft Windows.

The vulnerability could allow security feature bypass if an attacker installs an affected boot manager and bypasses Windows security features.This security update is rated Important for all supported editions of Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT 8.1, and Windows 10.

For more information, see the Affected Software and Vulnerability Severity Ratings section.The security update addresses the vulnerability by blacklisting affected boot managers.

For more information about the vulnerability see the Vulnerability Information section.For more information about this update, see Microsoft Knowledge Base Article 3179577.The following software versions or editions are affected.
Versions or editions that are not listed are either past their support life cycle or are not affected.

To determine the support life cycle for your software version or edition, see Microsoft Support Lifecycle.The following severity ratings assume the potential maximum impact of the vulnerability.

For information regarding the likelihood, within 30 days of this security bulletin’s release, of the exploitability of the vulnerability in relation to its severity rating and security impact, please see the Exploitability Index in the Aug bulletin summary.[1]This update is only available via Windows Update.[2]Windows 10 updates are cumulative.

The monthly security release includes all security fixes for vulnerabilities that affect Windows 10, in addition to non-security updates.

The updates are available via the Microsoft Update Catalog.*The Updates Replaced column shows only the latest update in any chain of superseded updates.

For a comprehensive list of updates replaced, go to the Microsoft Update Catalog, search for the update KB number, and then view update details (updates replaced information is provided on the Package Details tab).Note The vulnerability discussed in this bulletin affects Windows Server 2016 Technical Preview 5.

To be protected from the vulnerability, Microsoft recommends that customers running this operating system apply the current update, which is available from Windows Update. Secure Boot Security Feature Bypass Vulnerability – CVE-2016-3320A 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.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.The security update addresses the vulnerability by blacklisting affected boot managers.The following table contains links to the standard entry for each vulnerability in the Common Vulnerabilities and Exposures list:
Vulnerability title

CVE number

Publicly disclosed

Exploited

Secure Boot Security Feature Bypass Vulnerability

CVE-2016-3320

No

No

Mitigating FactorsThe following mitigating factors may be helpful in your situation:To exploit the vulnerability, an attacker must have either administrative privileges or physical access to the target device.
WorkaroundsThe following workarounds may be helpful in your situation:Configure BitLocker to use Trusted Platform Module (TPM)+PIN protection
To enable TPM and PIN protector, enable the enhanced protection group policy as follows:
Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives.
In the right-hand pane, double-click Require additional authentication at startup.
In the dialog box that appears, click Enabled.
Under Options, select Require TPM and Require startup PIN with TPM.
Click Apply and exit the Local Group Policy Editor.
Open the command prompt with Administrator privileges.
Enter the following command:

manage-bde -protectors -add c: <OR OS volume letter> -tpmandpin

When prompted for a PIN, enter a 4 or 6-digit PIN.
Restart the system.
Impact of workaround. 
The user will be required to enter the PIN every time the computer restarts.
How to undo the workaround
Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives
In the right-hand pane, double-click “Require additional authentication at startup”
In the dialog box that appears, click Enabled.
Under Options, select Allow TPM and Allow startup PIN with TPM.
Click Apply and exit the Local Group Policy Editor.
Restart the system.

Disable Secure Boot integrity protection of BitLocker
To disable Secure Boot, you must follow each of the steps in order.
Disable BitLocker
Open Control Panel and then click BitLocker Drive Encryption.
Click Turn off BitLocker
In the BitLocker Drive Encryption dialog box, click Turn off BitLocker.
Exit Control Panel.

Disable Secure Boot
Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives
Double-click Allow Secure Boot for integrity validation.
In the dialog box that appears, click Disabled.
Click Apply and exit the Local Group Policy Editor.

Re-enable BitLocker
Open Control Panel, then click BitLocker Drive Encryption.
Click Turn on BitLocker
In the BitLocker Drive Encryption dialog box, click Turn on BitLocker.
Exit Control Panel.

Impact of workaround. 
Disabling Secure Boot may cause systems to enter BitLocker recovery mode more often when you update firmware versions or BCD settings.
How to undo the workaround. 
Disable BitLocker
Open Control Panel, then click BitLocker Drive Encryption.
Click Turn off BitLocker
In the BitLocker Drive Encryption dialog box, click Turn off BitLocker.
Exit Control Panel.

Enable Secure Boot
Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives
Double-click Allow Secure Boot for integrity validation.
In the dialog box that appears, click Enabled.
Click Apply and exit the Local Group Policy Editor.

Re-enable BitLocker
Open Control Panel, then click BitLocker Drive Encryption.
Click Turn on BitLocker
In the BitLocker Drive Encryption dialog box, click Turn on BitLocker.
Exit Control Panel.

For Security Update Deployment information, see the Microsoft Knowledge Base article referenced here in the Executive Summary.Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See Acknowledgments for more information.The information provided in the Microsoft Knowledge Base is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose.
In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages.
Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.V1.0 (August 9, 2016): Bulletin published.
Page generated 2016-08-09 09:41-07:00.

Leave a Reply