Updated June 15: A correction has been made to the timeline dates.
As previously announced, security requirements have increased for Windows devices that use the Distributed Component Object Model (DCOM) or Remote Procedure Call (RPC) server technologies. Windows update releases starting June 2021 address a vulnerability in the DCOM remote protocol by progressively increasing security hardening in DCOM. Starting today, June 14, 2022, all DCOM clients attempting to establish connections to DCOM servers which have applied updates released June 14, 2022, or later, must either support an authentication level of RPC_C_AUTHN_LEVEL_PKT_INTEGRITY and higher or temporarily disable that enforcement by using the RequireIntegrityActivationAuthenticationLevel registry key in the DCOM server.
Note: We recommend that you update your devices to the latest security update available to take advantage of the advanced protections from the latest security threats.
When will this happen
Refer to the below timeline to understand the progressive hardening coming to DCOM.
- June 8, 2021 security update: Hardening changes are disabled by default but with the ability to enable them using a registry key.
- June 14, 2022 security update: Hardening changes are enabled by default but with the ability to disable them using a registry key.
- March 14, 2023 security update: Hardening changes are enabled by default with no ability to disable them. By this point, you must resolve any compatibility issues with the hardening changes and applications in your environment.
What you need to do to prepare
During the timeline phases in which hardening changes can be enabled or disabled (prior to March 14, 2023), users can use the following registry key:
Value Name: “RequireIntegrityActivationAuthenticationLevel”
Value Data: default = 0x00000000 means disabled. 0x00000001 means enabled. If this value is not defined, it will default to disabled. You must enter Value Data in hexadecimal format.
Devices must be restarted after setting this registry key, for it to take effect.
Note: Enabling the registry key above will make DCOM servers enforce an Authentication-Level of RPC_C_AUTHN_LEVEL_PKT_INTEGRITY or higher for activation.
To help identify the applications that might have compatibility issues after we enable DCOM security hardening changes, we added new DCOM error events in the System log:
Event 10036 is logged on the DCOM server and contains the IP address of the DCOM client.
Events 10037 and 10038 are logged on the DCOM client, not the DCOM Server machine.
The system will log these events if it detects that a DCOM client application is trying to activate a DCOM server using an authentication level that is less than RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. The client device can be traced from the server-side event log and the client-side event logs can be used to find the application.
If issues are encountered during testing, contact the vendor for the affected client or server software for an update or workaround, and see the DCOM errors supported by all Windows platforms.
It is important to ensure proper testing for this change. Please review the below documentation:
- Microsoft Docs > Open Specifications > [MS-DCOM]: Distributed Component Object Model (DCOM) Remote Protocol
- Microsoft App Development > Desktop Technologies > Networking and Internet > Remote Procedure Call > Authentication-Level Constants
- MSRC > Customer Guidance > Security Update Guide > Vulnerabilities > CVE 2021 26414
Message ID: MC392299
Published: 15 June 2022
Updated: 16 June 2022
Platform: World tenant