Description of the Security Only update for .NET Framework 3.5 SP1 for Windows Server 2012 (KB 4054175)

View products that this article applies to.

Summary

This security update resolves a security feature bypass vulnerability that exits 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.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.

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 Server 2012, see the following article in the Microsoft Knowledge Base:
  4055270 Security Only update for .NET Framework 3.5 SP2, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 updates for Windows Server 2012 (KB 4055270)

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, selectAdministrative Tools, and then selectMicrosoft Windows Server Update Services 3.0.
2. Expand ComputerName, and then selectAction.
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 4055270 in theSearchbox, and then selectSearch.
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. Click Import to import the packages to your WSUS server.
9. Select Close once the packages have been imported to return to WSUS.
   The updates are now available for installation through WSUS.

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 thePrograms 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 update KB 3122649.

File information

File hash

Package name	PackageHashSHA1	PackageHashSHA2
Windows8-RT-KB4054175-x64.msu	EAE7FCE3C31C6583F94541992FBDF91AB6FFD5A0	E40BB54AACAA71232C3441CB1335A8803630BC8E9EDFEB322B2FEC9DA93D1444
Windows8-RT-KB4054175-x86.msu	F4A271B8856E2EDF1E709D2FE35A447E37F2E274	134C7AF9B8D218A8B06596FD5965BDBB5DFEB200D212C93531D3AF38AF17CD7B

File attributes

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time together with your current daylight-saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.For all x86-based systemsFile name	File version	File size	Date	Time
smdiagnostics.dll	3.0.4506.8789	110,592	01-Dec-2017	13:05
smsvchost.exe	3.0.4506.8789	129,664	01-Dec-2017	13:05
system.data.sqlxml.dll	2.0.50727.8773	745,472	01-Dec-2017	13:05
system.identitymodel.dll	3.0.4506.8789	446,464	01-Dec-2017	13:05
system.runtime.serialization.dll	3.0.4506.8789	970,752	01-Dec-2017	13:05
system.runtime.serialization.dll	3.0.4506.8789	970,752	01-Dec-2017	13:05
system.servicemodel.dll	3.0.4506.8789	5,992,448	01-Dec-2017	13:05
system.servicemodel.washosting.dll	3.0.4506.8789	32,768	01-Dec-2017	13:05
system.servicemodel.dll	3.0.4506.8789	5,992,448	01-Dec-2017	13:05
system.xml.dll	2.0.50727.8773	2,056,192	01-Dec-2017	13:05
servicemonikersupport.dll	3.0.4506.8789	18,096	01-Dec-2017	13:05
system.identitymodel.dll	3.0.4506.8789	446,464	01-Dec-2017	13:05
system.runtime.serialization.dll	3.0.4506.8789	970,752	01-Dec-2017	13:05
system.servicemodel.dll	3.0.4506.8789	5,992,448	01-Dec-2017	13:05
For all x64-based systemsFile name	File version	File size	Date	Time
—	—	—	—	—
system.data.sqlxml.dll	2.0.50727.8773	745,472	01-Dec-2017	13:13
system.xml.dll	2.0.50727.8773	2,056,192	01-Dec-2017	13:13
servicemonikersupport.dll	3.0.4506.8789	20,144	01-Dec-2017	13:13
smdiagnostics.dll	3.0.4506.8789	94,208	01-Dec-2017	13:13
smsvchost.exe	3.0.4506.8789	117,376	01-Dec-2017	13:13
system.identitymodel.dll	3.0.4506.8789	405,504	01-Dec-2017	13:13
system.runtime.serialization.dll	3.0.4506.8789	847,872	01-Dec-2017	13:13
system.runtime.serialization.dll	3.0.4506.8789	847,872	01-Dec-2017	13:13
system.servicemodel.dll	3.0.4506.8789	5,332,992	01-Dec-2017	13:13
system.servicemodel.washosting.dll	3.0.4506.8789	32,768	01-Dec-2017	13:13
system.servicemodel.dll	3.0.4506.8789	5,332,992	01-Dec-2017	13:13
smdiagnostics.dll	3.0.4506.8789	110,592	01-Dec-2017	13:05
smsvchost.exe	3.0.4506.8789	129,664	01-Dec-2017	13:05
system.data.sqlxml.dll	2.0.50727.8773	745,472	01-Dec-2017	13:05
system.identitymodel.dll	3.0.4506.8789	446,464	01-Dec-2017	13:05
system.runtime.serialization.dll	3.0.4506.8789	970,752	01-Dec-2017	13:05
system.runtime.serialization.dll	3.0.4506.8789	970,752	01-Dec-2017	13:05
system.servicemodel.dll	3.0.4506.8789	5,992,448	01-Dec-2017	13:05
system.servicemodel.washosting.dll	3.0.4506.8789	32,768	01-Dec-2017	13:05
system.servicemodel.dll	3.0.4506.8789	5,992,448	01-Dec-2017	13:05
system.xml.dll	2.0.50727.8773	2,056,192	01-Dec-2017	13:05
servicemonikersupport.dll	3.0.4506.8789	18,096	01-Dec-2017	13:05
system.identitymodel.dll	3.0.4506.8789	446,464	01-Dec-2017	13:05
system.runtime.serialization.dll	3.0.4506.8789	970,752	01-Dec-2017	13:05
system.servicemodel.dll	3.0.4506.8789	5,992,448	01-Dec-2017	13:05

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

Applies to

This article applies to the following:

• Microsoft .NET Framework 3.5 Service Pack 1 when used with:
  • Windows Server 2012