Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Description of the Security Only update for .NET Framework 3.5.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB 4054176)


View products that this article applies to.

Summary

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

↑ Back to the top


Important

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

↑ Back to the top


Additional information about this security update

  • Enhanced Key Usage (EKU) is described in RFC 5280 in section 4.2.1.12. 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. With this change, besides requiring the appropriate client/server EKU on certificates, if the root certificate is disabled, the certificate chain validation will fail.

    When certificates are used for authentication, the authenticator examines the certificate that is provided by the remote endpoint and seeks 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 1.3.6.1.5.5.7.3.2. Likewise, 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 1.3.6.1.5.5.7.3.1. Certificates that have no EKU extension continue to authenticate correctly.

    First, 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” will opt out of the security changes.

  • For more information about this security update as it relates to Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1, see the following article in the Microsoft Knowledge Base:

4055269 Security Only update for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 updates for Windows 7 SP1 and Windows Server 2008 R2 SP1 (KB 4055269)

↑ Back to the top


How to obtain and install the update

Method 1: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog.

Method 2: Windows Software Update Services (WSUS)

On your WSUS server, follow these steps:

  1. Select Start, select Administrative Tools, and then select Microsoft Windows Server Update Services 3.0.
  2. Expand ComputerName, and then select Action.
  3. Select Import Updates.
  4. WSUS will open a browser window in which you may be prompted to install an ActiveX control. Install the ActiveX control to continue.
  5. Once the control is installed, you will see the Microsoft Update Catalog screen. Enter 4055269 in the Search box, and then select Search.
  6. Locate the .NET Framework packages that match the operating systems, languages, and processors in your environment. Select Add to add them to your basket.
  7. When you have selected all the packages you need, select View Basket.
  8. Select Import to import the packages to your WSUS server.
  9. Click Close once the packages have been imported to return to WSUS.

The updates are now available for installation through WSUS.

↑ Back to the top


Update deployment information

For deployment details for this security update, go to the following article 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

This update replaces updates KB 3122648 and KB 2973112.

↑ Back to the top


File information

File hash
Package name PackageHashSHA1 PackageHashSHA2
Windows6.1-KB4054176-ia64.msu 621D331BAB717F6E4C29190CAED47734A95E696E F4FBE62C0D0CA6676167274108CB0A634CCDAFE261057C39A0BAB17960609F6C
Windows6.1-KB4054176-x86.msu 10383B165D3126026B6E642BC45C5FB2E74BF58B 392E3DB13DC85491CA42A896092EC7A5641B15BBA951877B4081FFA196ACB2A7
Windows6.1-KB4054176-x64.msu C7C6C0CFDE80925E0278BDAEF17663D7CDAE3269 3BF194121E972E8C5DC28CC0C2DD5E8486585148F374F528F25B775B1A0083F0

 

 

↑ Back to the top


How to obtain help and support for this security update

↑ Back to the top


Applies to

This article applies to the following:
  • Microsoft .NET Framework 3.5.1 when used with:
    • Windows Server 2008 R2 Service Pack 1
    • Windows 7 Service Pack 1
 

↑ Back to the top


Keywords: kbsurveynew, kbsecvulnerability, kbsecurity, kbsecreview, kbsecbulletin, kbbug, kblangall, kbfix, kbexpertiseinter, kb, atdownload, kbmustloc

↑ Back to the top

Article Info
Article ID : 4054176
Revision : 23
Created on : 1/20/2018
Published on : 1/20/2018
Exists online : False
Views : 16