CVE-2016-3287

Меры по смягчению последствий

The 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.

Обходное решение

Configure BitLocker to use Trusted Platform Module (TPM)+PIN protection To enable TPM and PIN protector, enable the enhanced protection group policy as follows:

1. Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
2. Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives.
3. In the right-hand pane, double-click Require additional authentication at startup.
4. In the dialog box that appears, click Enabled.
5. Under Options, select Require TPM and Require startup PIN with TPM.
6. Click Apply and exit the Local Group Policy Editor.
7. Open the command prompt with Administrator privileges.
8. Enter the following command:

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

9. When prompted for a PIN, enter a 4 or 6-digit PIN.
10. 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

1. Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
2. Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives
3. In the right-hand pane, double-click “Require additional authentication at startup”
4. In the dialog box that appears, click Enabled.
5. Under Options, select Allow TPM and Allow startup PIN with TPM.
6. Click Apply and exit the Local Group Policy Editor.
7. Restart the system.

Disable Secure Boot integrity protection of BitLocker To disable Secure Boot, you must follow each of the steps in order.

1. Disable BitLocker
   1. Open Control Panel and then click BitLocker Drive Encryption.
   2. Click Turn off BitLocker
   3. In the BitLocker Drive Encryption dialog box, click Turn off BitLocker.
   4. Exit Control Panel.
2. Disable Secure Boot
   1. Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
   2. Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives
   3. Double-click Allow Secure Boot for integrity validation.
   4. In the dialog box that appears, click Disabled.
   5. Click Apply and exit the Local Group Policy Editor.
3. Re-enable BitLocker
   1. Open Control Panel, then click BitLocker Drive Encryption.
   2. Click Turn on BitLocker
   3. In the BitLocker Drive Encryption dialog box, click Turn on BitLocker.
   4. 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.

1. Disable BitLocker
   1. Open Control Panel, then click BitLocker Drive Encryption.
   2. Click Turn off BitLocker
   3. In the BitLocker Drive Encryption dialog box, click Turn off BitLocker.
   4. Exit Control Panel.
2. Enable Secure Boot
   1. Click Start, click Run, type gpedit.msc, and then click OK to open the Local Group Policy Editor.
   2. Under Local Computer Policy, navigate to Administrative Templates>Windows Components>BitLocker Drive Encryption>Operating Systems Drives
   3. Double-click Allow Secure Boot for integrity validation.
   4. In the dialog box that appears, click Enabled.
   5. Click Apply and exit the Local Group Policy Editor.
3. Re-enable BitLocker
   1. Open Control Panel, then click BitLocker Drive Encryption.
   2. Click Turn on BitLocker
   3. In the BitLocker Drive Encryption dialog box, click Turn on BitLocker.
   4. Exit Control Panel.

FAQ

I am running Windows Server 2012. Do I need to install the 3170377 and 3172727 updates in a particular order? No. The 3170377 and 3172727 updates both contain the same components and can be installed in any order. Installing one and then the other without a system restart in between is allowed; however, if you install the 3172727 update first and then restart the system, subsequent attempts to install the 3170377 update will display the message, “The update is not applicable to your computer." This is because the 3172727 update supersedes the 3170377 update by design.