Gamingdeputy News on February 17, Microsoft disclosed in June 2021 a security feature bypass (CVE-2021-26414) vulnerability in the Distributed Component Object Model (DCOM). Microsoft issued a reminder today,Said that next month in win10,win11 DCOM enhancements are enabled by default on Windows Server and Windows Server.
According to Microsoft’s official customized schedule, DCOM hardening changes will be enabled by default on March 14, 2023, and users cannot disable them.
Gamingdeputy attaches Microsoft’s official introduction:
Distributed Component Object Model (DCOM) Remoting Protocol is a protocol for exposing application objects using Remote Procedure Calls (RPC).DCOM is used for communication between software components of network devices.CVE-2021-26414 requires hardening changes in DCOM. Therefore, it is recommended to verify that client or server applications using DCOM or RPC in the environment are working as expected and enable hardening changes.
The first phase of the DCOM update was released on June 8, 2021. In this update, DCOM hardening is disabled by default. They can be enabled by modifying the registry, as described in the “Registry settings to enable or disable hardening changes” section below.The second phase of the DCOM update will be released on June 14, 2022. This has changed hardening to be enabled by default, but kept the ability to disable the change using a registry key setting.The final phase of the DCOM update will be released in March 2023. It will leave DCOM hardening enabled and remove the ability to disable it.
We know that DCOM hardening changes can cause app compatibility issues in your environment.The latest security updates released in November 2022 include the following features to easily manage this migration:
New DCOM error events – To help identify applications that may have compatibility issues after enabling DCOM security hardening changes, we have added new DCOM error events to the system log. See below for details on the release timeline and supported platforms.
Authentication level for all non-anonymous activation requests – To help reduce app compatibility issues, we automatically increase the authentication level for all non-anonymous activation requests from Windows-based DCOM clients to at least RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. With this change, most Windows-based DCOM client requests will be automatically accepted, enabling the DCOM hardening changes on the server side without any further modifications to the DCOM client.
While we recommend that you install the latest security updates, we also want to give you more control if your environment does not have the latest security updates installed.
Enable DCOM hardening.If the June 14, 2022 or later update has not been installed, all DCOM servers can be RequireIntegrityActivationAuthenticationLevel The registry key is set to 1. This will enable DCOM hardening in your environment.
Increase the level of authentication.If you have not installed the November 8, 2022 or later update, you can set the RaiseActivationAuthenticationLevel The registry key is set to 2.This increases the authentication level of all non-anonymous activation requests from Windows-based DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY.
It is recommended to complete testing in the environment and enable these hardening changes as soon as possible. If an issue is discovered during testing, the affected client or server software vendor must be contacted for an update or workaround before the March 2023 Update is released.
Note It is strongly recommended to install the latest security update available. They provide advanced protection against the latest security threats, as well as features we’ve added to support migration.For more information and context on how to harden DCOM , see DCOM Authentication Hardening: What You Need to Know.
updated version | behavior change |
June 8, 2021 | Hardening changes are disabled by default, but they can be enabled using a registry key. |
June 14, 2022 | Hardening changes enabled by default, but can be disabled using a registry key. |
November 8, 2022 | In response to your feedback, the November 8, 2022 Update includes a patch for clients (devices, applications, or services acting as DCOM clients). This patch automatically increases the authentication level for all non-anonymous activation requests to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY. If you use a third-party Windows DCOM client application and depend on the software provider to increase the activation authentication level to support the DCOM hardening changes, this hotfix removes the dependency. This allows to automatically increase the activation authentication level at the Windows OS level. This prevents DCOM servers that enable DCOM hardening changes from rejecting activation requests. |
March 14, 2023 | Hardening changes are enabled by default, but there is no way to disable them. At this point, any compatibility issues with hardening changes and applications in the environment must be resolved. |