CVE-2022-38023: Netlogon RPC Elevation of Privilege Vulnerability

Overview

Severity
High (CVSS 8.1)
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Category
Elevation of Privilege
Exploit Status
Not Exploited
Exploitation Likelihood
More Likely
Patch Tuesday
2022-Nov
Released
2022-11-08
Last Updated
2023-07-18
EPSS Score
0.35% (percentile: 57.8%)

FAQ

Does this vulnerability affect client operating systems? This vulnerability only applies the Windows Server versions listed in the Security Update table. Where can I find more information about these changes? For more information please see How to manage Netlogon Protocol changes related to CVE-2022-38023. I am running Windows Server 2022 Datacenter: Azure Edition (Server Core) but the hotpatch (Windows Server 2022 Datacenter: Azure Edition (Hotpatch)) for it is not listed in the Security Updates table. Is there an update that I can apply for this edition of Windows Server 2022? The update to address this vulnerability for Windows Server 2022 Datacenter: Azure Edition (Server Core) is not hotpatchable and is therefore not included in the November Hotpatch KB (5019080). Customers running Windows Server 2022 Datacenter: Azure Edition (Server Core) as a domain controller should install the update for Windows Server 2022 (5019081). This update will require a computer restart. What privileges could be gained by an attacker who successfully exploited the vulnerability? An attacker who successfully exploited this vulnerability could gain administrator privileges. According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? Successful exploitation of this vulnerability requires an attacker to gather information specific to the environment of the targeted component. How could an attacker exploit this vulnerability? An authenticated attacker could leverage cryptographic protocol vulnerabilities in the Windows Netlogon protocol when RPC Signing is used instead of RPC Sealing. Where RPC Signing is used instead of RPC Sealing the attacker could gain control of the service and then might be able to modify Netlogon protocol traffic to elevate their privileges. How does Microsoft plan to address this vulnerability? To give administrators time to make corrections that prevent authentication failures, and to provide a choice on when

Affected Products (16)

Windows

  • Windows Server 2019
  • Windows Server 2019 (Server Core installation)
  • Windows Server 2022
  • Windows Server 2022 (Server Core installation)
  • Windows Server 2016
  • Windows Server 2016 (Server Core installation)

ESU

  • Windows Server 2008 for 32-bit Systems Service Pack 2
  • Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
  • Windows Server 2008 for x64-based Systems Service Pack 2
  • Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
  • Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
  • Windows Server 2012
  • Windows Server 2012 (Server Core installation)
  • Windows Server 2012 R2
  • Windows Server 2012 R2 (Server Core installation)

Security Updates (11)

Revision History

  • 2022-11-08: Information published.
  • 2023-04-11: Microsoft is announcing the release of the second phase of Windows security updates to address this vulnerability. The April 2023 updates remove the ability to disable RPC sealing by setting value 0 to the RequireSeal registry subkey. Please see How to manage Netlogon Protocol changes related to CVE-2022-38023 for more information, including the planned enforcement timeline.
  • 2023-06-13: Updated FAQ information. This is an informational change only.
  • 2023-07-11: Microsoft is announcing the release of the fourth phase of Windows security updates to address this vulnerability. The July 2023 updates remove the ability to set value 1 to the RequireSeal registry subkey and enables the Enforcement phase. Please see How to manage Netlogon Protocol changes related to CVE-2022-38023 for more information, including the planned enforcement timeline.
  • 2023-07-18: Removed the Security Hotpatch Update for the July 2023 revision as that package doesn't exist for this release cycle. You must install the Security Update to get the updated software.