Summary
This security update resolves a Microsoft SharePoint Server remote code execution vulnerability and Microsoft SharePoint Server security feature bypass vulnerability. To learn more about the vulnerabilities, see the following security advisories:
-
Microsoft Common Vulnerabilities and Exposures CVE-2023-21742
-
Microsoft Common Vulnerabilities and Exposures CVE-2023-21743
-
Microsoft Common Vulnerabilities and Exposures CVE-2023-21744
Notes:
-
This is build 16.0.5378.1000 of the security update package.
-
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:
Improvements and fixes
This security update contains fixes for the following nonsecurity issues in Project Server:
-
The display name of the Project Detail Page (PDP) isn't updated correctly.
-
Occasionally, administrators may have to restore server metadata, such as the enterprise custom fields. Although the restore process starts the Reporting Database Refresh queue job, the following items might occur:
-
The queue job fails.
-
When you access reporting data either directly from the reporting schema or through Open Data Protocol (OData), no data is returned.
-
In the Universal Logging Service logs, the following error is reported:
SPValidatingBinder: blocked type Microsoft.Office.Project.Server.BusinessLayer.ReportingLayer.RefreshStorageData denied.
This update fixes the problem so that the Reporting Database Refresh job finishes successfully.
-
Known issues in this update
After you install this security update, you may be unable to browse to a SharePoint site if the site has a blocked file type extension in the URL. For more information, see "The URL is invalid" error when you browse to a SharePoint site (KB5023406).
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.
More information
Security update deployment information
For deployment information about this update, see Deployments - Security Update Guide.
Security update replacement information
This security update replaces previously released security update 5002321.
File hash information
|
File name |
SHA256 hash |
|---|---|
|
sts2016-kb5002338-fullfile-x64-glb.exe |
F19D318CDCF9498E9AEB3A4623F03CAC0632E80097F42DE79A7543EDEBAEFD43 |
File information
Download the list of files that are included in security update 5002338.
Information about protection and security
Protect yourself online: Windows Security support
Learn how we guard against cyber threats: Microsoft Security
Change history
The following table summarizes some of the most important changes to this topic.
|
Date |
Description |
|---|---|
|
January 31, 2023 |
Added a "Known issues in this update" section to describe an issue that users may experience. |
