Description of the security update for SharePoint Enterprise Server 2016: April 14, 2020

This security update resolves remote code execution vulnerabilities that exists in Microsoft SharePoint if the software does not check the source markup of an application package. This update also resolves cross-site-scripting (XSS) vulnerabilities that exists if Microsoft SharePoint Server does not correctly sanitize a specially crafted web request to an affected SharePoint server.

To learn more about these vulnerabilities, see the following security advisories: 

• Microsoft Common Vulnerabilities and Exposures CVE-2020-0920
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0923
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0924
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0925
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0926
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0927
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0929
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0930
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0931
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0932
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0933
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0954
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0971
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0972
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0973
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0974
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0975
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0976
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0977
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0978
• Microsoft Common Vulnerabilities and Exposures CVE-2020-0980

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 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:

• New features included in the November 2016 Public Update for SharePoint Server 2016 (Feature Pack 1)
• New features included in the September 2017 Public Update for SharePoint Server 2016 (Feature Pack 2)

This security update contains improvements and fixes for the following nonsecurity issues in SharePoint Server 2016:

• Because Brazil no longer observes daylight saving time, date and time values are displayed incorrectly for list items in site collections that use the "(UTC-03:00) Brasilia" and "(UTC-04:00) Cuiaba" time zones.
• If a list has many columns and security scopes but fewer than the List View Threshold setting (the default setting is 5,000), it may take long time to open the list because of a slow response from the database server. 
• Enterprise keywords can't be saved in the NewDocSet.aspx page after you add another metadata column to the document set. 
• When you use two separate accounts for the object cache, the publishing sites collections may intermittently display a "Sorry something went wrong" error message. 
• Word 2016 crashes when you try to save certain documents.
• Mixtures of Traditional Chinese and other text are not handled correctly by the Chinese Traditional Word Breaker.