This security update resolves a cross-site-scripting (XSS) vulnerability that exists if Microsoft SharePoint Server does not correctly sanitize a specially crafted web request to an affected SharePoint server. To learn more about the vulnerability, see the following:
- Microsoft Common Vulnerabilities and Exposures CVE-2019-1201
- Microsoft Common Vulnerabilities and Exposures CVE-2019-1202
- Microsoft Common Vulnerabilities and Exposures CVE-2019-1203
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:
Improvements and fixes
This security update contains the following improvements in SharePoint Enterprise Server 2016:
Improved SharePoint search compatibility with PDF files.
General improvements for notebooks in folders that are synced through OneDrive.
This security update contains fixes for the following nonsecurity issues in SharePoint Enterprise Server 2016:
Fix: When a validation is added to a column within a document library, folder creation fails and generates a "Cannot create folder" error message.
Fix: Search and Distributed Cache servers in a MinRole farm that have custom web templates display "Upgrade Required" after you run an in-place build-to-build upgrade. After this update is applied, the servers display "No Action Required."
Fix: When you try to run a SharePoint Designer 2013 Workflow as a user if you have an ampersand character in your username, or in a domain that has an ampersand character in its name, the workflow fails.
Fix: When a website URL contains a space, the Newsfeed link to it fails.
This security update contains improvements and fixes for the following nonsecurity issues in Project Server 2016:
Through the client-side object model (CSOM), the TaskLink ProjUid property for an external task returns the ID of its own project instead of the ID of the project that the task refers to. This update adds the ExternalProjectUid and ExternalTaskUid properties to the Task class to fix this issue.
Fix: When the database upgrade sequence of the SharePoint Server 2016 Products Configuration Wizard runs, the Central Admin Database is unexpectedly added to the Project Server database schema. This may cause reporting issues and violations to health rules to run against the Central Admin Database.
Fix: When you view the resource engagements Resource Requests page that is formatted to show timephased data, it may take several minutes for the page to render, depending on the number and complexity of the engagements.
Fix: The CalendarException.RecurrenceWeek property returns the wrong value through the client-side object model (CSOM).
Fix: When the Schedule Variance Percentage (SVP) earned value field becomes very large, an overflow condition occurs that prevents PWA project views from loading.
Fix: The project Start Date that is displayed in Project Detail Pages (PDPs) in Project Web App (PWA) doesn't match what is displayed in the Project Information dialog box in Project Professional 2016.
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.
Security update deployment information
For deployment information about this update, see security update deployment information: August 13, 2019.
Security update replacement information
This security update replaces previously released security update 4475520.
File hash information
|File name||SHA1 hash||SHA256 hash|