This update is included in the February 2018 Preview of the Quality Rollups for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 for Windows Server 2008 SP2 (KB 4074808). Parts of this update were previously included in the Security and Quality rollup (KB 4076495) on February 13, 2018, in the Preview of Quality rollup (KB 4057273) on January 17, 2018 and as part of the Security and Quality rollup (KB 4055267) on January 9, 2018.
This security update resolves a security feature bypass vulnerability that exists when Microsoft .NET Framework and .NET Core components do not completely validate certificates. This security update addresses the vulnerability by helping to make sure that .NET Framework and .NET Core components completely validate certificates. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-0786.
Additionally, this security update resolves a denial of service vulnerability that exists when .NET Framework and .NET core components incorrectly process XML documents. This update addresses the vulnerability by correcting how .NET Framework and .NET Core component applications handle XML document processing. To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2018-0764.
- If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.
Additional information about this security update
- Enhanced Key Usage (EKU) is described in RFC 5280 in section 22.214.171.124. This extension indicates one or more purposes for which the certified public key may be used in addition to or instead of the basic purposes that are indicated in the key usage extension. For example, a certificate that is used for the authentication of a client to a server must be configured for Client Authentication. Similarly, a certificate that is used for the authentication of a server must be configured for Server Authentication. After this change is made, if the root certificate is disabled, the certificate chain validation fails. Thsi is in addition to requiring the appropriate client or server EKU on certificates.
When certificates are used for authentication, the authenticator examines the certificate that is provided by the remote endpoint and tries the correct purpose object identifier in Application Policies extensions. When a certificate is used for client authentication, the object identifier for Client Authentication must be present in the EKU extensions of the certificate, or authentication fails. The object identifier for Client Authentication is 126.96.36.199.188.8.131.52.2. Similarly, when a certificate is used for server authentication, the object identifier for Server Authentication must be present in the EKU extensions of the certificate, or authentication fails. The object identifier for Server Authentication is 184.108.40.206.220.127.116.11.1. Certificates that have no EKU extension continue to authenticate correctly.
Consider making changes to your component’s certificates to make sure that they are using the correct EKU OID attributes and are secured correctly. If you temporarily cannot access correctly reissued certificates, you can choose to opt in or out of the security change to avoid any connectivity effects. To do this, specify the following appsetting in the configuration file:
<appSettings> <add key="wcf:useLegacyCertificateUsagePolicy" value="true" /></appSettings>Note Setting the value to “true” opts out of the security changes.
- For more information about this security update as it relates to Windows Server 2008 Service Pack 2, see the following articles in the Microsoft Knowledge Base:
4074808 February 2018 Preview of the Quality Rollups for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 for Windows Server 2008 SP2 (KB 4074808)
4076495 Security and Quality Rollup for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 for Windows Server 2008 SP2 (KB 4076495)
4057273 January 2018 Preview of the Quality Rollups for .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 for Windows Server 2008 SP2 (KB 4057273)
4055267 Security and Quality Rollup for the .NET Framework 2.0 SP2, 3.0 SP2, 4.5.2, and 4.6 updates for Windows Server 2008 SP2 (KB 4055267)
How to obtain and install the update
Method 1: Windows Update
This update is available through Windows Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to get security updates automatically, see Windows Update: FAQ.
Method 2: Microsoft Update Catalog
To get the stand-alone package for this update, go to update KB 4074808.
Method 3: Windows Software Update Services (WSUS)
On your WSUS server, follow these steps:
- Select Start, select Administrative Tools, and then select Microsoft Windows Server Update Services 3.0.
- Expand ComputerName, and then select Action.
- Select Import Updates.
Note WSUS opens a browser window in which you may be prompted to install an ActiveX control. Install the ActiveX control to continue.
- After the control is installed, you will see the Microsoft Update Catalog screen. Enter 4074808 in the Search box, and then select Search.
- Locate the .NET Framework packages that match the operating systems, languages, and processors in your environment. Select Add to add them to your basket.
- After you select all the packages that you require, select View Basket.
- To import the packages to your WSUS server, select Import.
- To return to WSUS, select Close after the packages are imported.
The updates are now available for installation through WSUS.
Update deployment information
For deployment details for this security update, go to the following articles in the Microsoft Knowledge Base:
20180109 Security update deployment information: January 9, 2018
Update removal information
Note We do not recommend that you remove any security update. To remove this update, use the Programs and Features item in Control Panel.
Update restart information
This update does not require a system restart after you apply it unless files that are being updated are locked or are being used.
Update replacement information
How to obtain help and support for this security update
- Help for installing updates: Windows Update FAQ
- Security solutions for IT professionals: TechNet Security Support and Troubleshooting
- Help for protecting your Windows-based products and services from viruses and malware: Microsoft Secure
- Local support according to your country: International Support