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 update for SharePoint Enterprise Server 2016: July 9, 2019


View products that this article applies to.

Summary

This security update resolves an Authentication Bypass vulnerability that allows SAML tokens to be signed by using arbitrary symmetric keys in Windows Communication Foundation (WCF) and Windows Identity Foundation (WIF). To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2019-1006 and Microsoft Common Vulnerabilities and Exposures CVE-2019-1134.

Note To apply this security update, you must have the release version of Microsoft SharePoint Enterprise Server 2016 installed on the computer.

This public update delivers Feature Pack 2 for SharePoint Server 2016. Feature Pack 2 contains the following feature:

  • SharePoint Framework (SPFx)

This public update also delivers all the features that were included in Feature Pack 1 for SharePoint Server 2016, including:

  • Administrative Actions Logging
  • MinRole enhancements
  • SharePoint Custom Tiles
  • Hybrid Auditing (preview)
  • Hybrid Taxonomy
  • OneDrive API for SharePoint on-premises
  • OneDrive for Business modern user experience (available to Software Assurance customers)

The OneDrive for Business modern user experience requires an active Software Assurance contract at the time that the experience is enabled, either by installation of the public update or by manual enablement. If you don't have an active Software Assurance contract at the time of enablement, you must turn off the OneDrive for Business modern user experience.

For more information, see the following Microsoft Docs articles:

↑ Back to the top


Improvements and fixes

This update contains the following improvements in SharePoint Server 2016:

  • Adds support for the new Japanese era name to the Chinese word breaker to make sure that the name will be broken correctly.

  • Makes general improvements for notebooks that are located in folders that are synced through OneDrive.

Contains fixes for the following nonsecurity issues in SharePoint Server 2016:

  • You can‘t create a subsite based on a template that includes content in a site collection that has a retention policy.

  • Query Builder takes a long time to load or times out if there are many managed properties (for example, more than 10 thousand) in the Search service application (SSA).

  • Fixes an error when re-executing the backup and restore operations after executing the backup and restore operations with UI mode.

  • Fixes an issue in which resetting the role inheritance by using the SPWeb.ResetRoleInheritance method does not work on copied sites that are created by using the Copy-SPSite cmdlet.

  • In some cases, existing files are overwritten even if users don’t explicitly overwrite the files.

Contains the following improvements and fixes for nonsecurity issues in Project Server 2016:

  • Makes changes so that the first year of an era in Japanese dates on a timeline view shows as the special Kanji character (元). The Japanese date format is now consistent between the calendar date picker and the timeline view.

  • You can now update a task dependency lead and lag time by using the LinkLagDuration property through the client-side object model (CSOM). Similar to other duration properties (such as the Task.Duration property in the Task Object), LinkLagDuration accepts either a string or an integer value, such as "1d" or "480" to indicate one day of work.

  • After you change actual work values in a timesheet, you find that the columnar Total work values in the time-phased grid part of the view does not sum correctly.

  • When you query project-level information through the client-side object model (CSOM), read performance is slow if the Project Owner field is included.

↑ Back to the top


How to get and install the update

Method 1: Microsoft Update

This update is available from Microsoft 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 standalone package for this update, go to the Microsoft Update Catalog website.

Method 3: Microsoft Download Center

You can get the standalone update package through the Microsoft Download Center. Follow the installation instructions on the download page to install the update.

↑ Back to the top


More Information

Security update deployment information

For deployment information about this update, see security update deployment information: July 9, 2019.

Security update replacement information

This security update replaces previously released security update 4464594.

File hash information

File name SHA1 hash SHA256 hash
sts2016-kb4475520-fullfile-x64-glb.exe 81E7F45B22FCF7257ACEEDA232EE24C55F9B8D63 C06799126163D7863F2F98D903296BFA0F2ACB063B14869F03933844228595B5


File information

Download the list of files that are included in security update 4475520.

↑ Back to the top


How to get help and support for this security update

Help for installing updates: Protect yourself online

Help for protecting your Windows-based computer from viruses and malware: Microsoft Security

Local support according to your country: International Support

↑ Back to the top


Keywords: kbBug, kbfix, kbsurveynew, kbExpertiseInter, kbSecReview, KbSECVulnerability, ATdownload, kbMustLoc, kbLangAll, kbSecurity, Vulnerabilities/exploits/security bulletins, kbContentAuto, kbSupportTopic, KbSECBulletin

↑ Back to the top

Article Info
Article ID : 4475520
Revision : 20
Created on : 11/15/2019
Published on : 11/15/2019
Exists online : False
Views : 258