CVE-2022-41089: .NET Framework Remote Code Execution Vulnerability

Overview

Severity
High (CVSS 7.8)
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Category
Remote Code Execution
Exploit Status
Not Exploited
Exploitation Likelihood
Less Likely
Patch Tuesday
2022-Dec
Released
2022-12-13
Last Updated
2023-06-30
EPSS Score
4.52% (percentile: 89.2%)

FAQ

According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution? The word Remote in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. For example, when the score indicates that the Attack Vector is Local and User Interaction is Required, this could describe an exploit in which an attacker, through social engineering, convinces a victim to download and open a specially crafted file from a website which leads to a local attack on their computer.

Affected Products (96)

Developer Tools

  • Microsoft Visual Studio 2022 version 17.2
  • Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
  • Microsoft Visual Studio 2022 version 17.0
  • Microsoft Visual Studio 2022 version 17.4
  • .NET 6.0
  • .NET Core 3.1
  • .NET 7.0
  • PowerShell 7.2
  • PowerShell 7.3
  • Microsoft .NET Framework 4.8 on Windows Server 2012 R2
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft .NET Framework 4.8 on Windows Server 2012 (Server Core installation)
  • Microsoft .NET Framework 4.8 on Windows 8.1 for 32-bit systems
  • Microsoft .NET Framework 4.8 on Windows Server 2016
  • Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for x64-based Systems
  • Microsoft .NET Framework 4.8 on Windows Server 2012
  • Microsoft .NET Framework 4.8 on Windows Server 2016 (Server Core installation)
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for x64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 1809 for ARM64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019
  • Microsoft .NET Framework 4.8 on Windows 7 for x64-based Systems Service Pack 1
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2019 (Server Core installation)
  • Microsoft .NET Framework 4.8 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
  • Microsoft .NET Framework 4.8 on Windows 7 for 32-bit Systems Service Pack 1
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H1 for ARM64-based Systems
  • Microsoft .NET Framework 4.8 on Windows Server 2012 R2 (Server Core installation)
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H1 for x64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H1 for 32-bit Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows Server 2022 (Server Core installation)
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 20H2 for 32-bit Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 20H2 for ARM64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 11 version 21H2 for x64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for ARM64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for 32-bit Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 11 version 21H2 for ARM64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for 32-bit Systems
  • Microsoft .NET Framework 3.5 AND 4.8 on Windows 10 Version 21H2 for x64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for ARM64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019 (Server Core installation)
  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows Server 2019
  • Microsoft .NET Framework 3.5 AND 4.7.2 on Windows 10 Version 1809 for x64-based Systems
  • Microsoft .NET Framework 4.8 on Windows RT 8.1
  • Microsoft .NET Framework 4.8 on Windows 10 Version 1607 for 32-bit Systems
  • Microsoft .NET Framework 4.8 on Windows 8.1 for x64-based systems
  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022
  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows Server 2022 (Server Core installation)
  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 21H2 for x64-based Systems
  • Microsoft .NET Framework 3.5 AND 4.8.1 on Windows 11 version 21H2 for ARM64-based Systems
  • ... and 46 more

Security Updates (38)

Acknowledgments

<a href="https://twitter.com/monoxgas">Nick Landers</a> with NetSPI, <a href="https://twitter.com/lefterispan">Eleftherios Panos</a> with <a href="https://www.nettitude.com/">Nettitude</a>, <a href="https://twitter.com/monoxgas">Nick Landers</a> with NetSPI

Revision History

  • 2022-12-13: Information published.
  • 2022-12-19: In the Security Updates table corrected the severity entry for Microsoft .NET Framework 3.5 AND 4.8.1 installed on Windows Server 2022. This is an informational change only. Customers who have successfully installed the update do not need to take any further action.
  • 2023-01-25: Revised the Security Updates table to include PowerShell 7.2 and PowerShell 7.3 because these versions of PowerShell 7 are affected by this vulnerability. See https://github.com/PowerShell/Announcements/issues/37 for more information.
  • 2023-06-30: To address a known issue when after installing the December 13, 2022, updates for .NET Framework and .NET, users may have experienced issues with how WPF-based applications render XPS documents, Microsoft has released the June 2023 security updates for .NET Framework and for .NET. We recommend that customers install the June 2023 updates. Please note that if you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. To remove either of the workarounds see the instructions for removal in the &quot;Alternative Workaround&quot; section of KB5022083 Change in how WPF-based applications render XPS documents.