Summary
This security update resolves a Microsoft SharePoint Server spoofing vulnerability. To learn more about the vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2023-28288.
Notes:
-
This is build 16.0.5391.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
To help customers secure their environments, Microsoft is introducing integration between SharePoint Server 2016 and the Windows Antimalware Scan Interface (AMSI). The AMSI integration functionality is designed to prevent malicious web requests from reaching SharePoint endpoints. For example, it prevents the exploitation of a security vulnerability in a SharePoint endpoint before the official fix for the security vulnerability is installed. For more information, see Configure AMSI integration with SharePoint Server.
Note: To get the improvement, you have to install KB 5002370 together with this update.
This security update also contains an improvement and a fix for the following nonsecurity issue in SharePoint Enterprise Server 2016:
-
Ensure that the SharePoint farm service account is in the database owner group of a subscription settings service application database.
-
Fixes an issue in which blocked file extensions cause errors in folder and subsite creation and accessing.
Known issues in this update
After you install this security update for SharePoint Server 2016 running on Windows Server 2012 R2, you will receive an "HTTP Error 503. The service is unavailable" error message. For more information and the workaround for this known issue, see HTTP Error 503 after installing April 11, 2023 updates for SharePoint Server 2016 on Windows Server 2012 R2 (KB5026765).
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 5002368.
File hash information
|
File name |
SHA256 hash |
|---|---|
|
sts2016-kb5002385-fullfile-x64-glb.exe |
8D51EE29A7751D553B0BD952FD714502A845EBFEEC08D43F86129C7C4D4B6E9E |
File information
Download the list of files that are included in security update 5002385.
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 |
|---|---|
|
April 18, 2023 |
Added a "Known issues in this update" section to describe an issue that users may experience. |
