Skip to content

GHSA-8f7f-vqg5-jrv9 BIT-dotnet-2023-21538 BIT-dotnet-sdk-2023-21538 BIT-powershell-2023-21538 CVE-2023-21538

.NET Denial of Service Vulnerability

High NuGet
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
2.84%
Chance of exploitation in the next 30 days. Higher than 86.66% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-502 Deserialization of Untrusted Data
Fix
Available
12 packages have a fixed version

Description

Microsoft Security Advisory CVE-2023-21538: .NET Denial of Service Vulnerability

<a name="executive-summary"></a>Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A denial of service vulnerability exists in .NET 6.0 where a malicious client could cause a stack overflow which may result in a denial of service attack when an attacker sends an invalid request to an exposed endpoint.

Discussion

Discussion for this issue can be found at https://github.com/dotnet/runtime/issues/80449

<a name="mitigation-factors"></a>Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

<a name="affected-software"></a>Affected software

  • Any .NET 6.0 application running on .NET 6.0.12 or earlier.

If your application uses the following package versions, ensure you update to the latest version of .NET.

<a name=".NET 6"></a>.NET 6
Package name Affected version Patched version
Microsoft.NetCore.App.Runtime.linux-arm >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.linux-arm64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.linux-musl-arm >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.linux-musl-arm64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.linux-musl-x64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.linux-x64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.osx-arm64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.osx-x64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.win-arm >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.win-arm64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.win-x64 >= 6.0.0, <= 6.0.12 6.0.13
Microsoft.NetCore.App.Runtime.win-x86 >= 6.0.0, <= 6.0.12 6.0.13

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

If you have a runtime or SDK with a version listed, or an affected package listed in affected software, you're exposed to the vulnerability.

<a name="how-fix"></a>How do I fix the issue?
  • To fix the issue please install the latest version of .NET 6.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
  • If you have .NET Core 3.1 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;
  • If you are using one of the affected packages, please update to the patched version listed above.
.NET Core SDK (reflecting any global.json):

 Version:   6.0.300
 Commit:    8473146e7d

Runtime Environment:

 OS Name:     Windows
 OS Version:  10.0.18363
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.300\

Host (useful for support):

  Version: 6.0.5
  Commit:  8473146e7d

.NET Core SDKs installed:

  6.0.300 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:

  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

.NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

Other Information

Reporting Security Issues

If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to secure@microsoft.com. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

External Links

CVE-2023-21538

Revisions

V1.0 (January 10, 2023): Advisory published.

Version 1.0

Last Updated 2023-01-10

Affected versions

NuGet

PackageVulnerableFixed in
Microsoft.NETCore.App.Runtime.linux-arm
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.linux-arm64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.linux-musl-arm
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.linux-musl-arm64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.linux-musl-x64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.linux-x64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.osx-arm64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.osx-x64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.win-arm
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.win-arm64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.win-x64
>= 6.0.0, < 6.0.13
6.0.13
Microsoft.NETCore.App.Runtime.win-x86
>= 6.0.0, < 6.0.13
6.0.13

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

Microsoft.NETCore.App.Runtime.linux-arm NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-arm --version 6.0.13

Microsoft.NETCore.App.Runtime.linux-arm64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-arm64 --version 6.0.13

Microsoft.NETCore.App.Runtime.linux-musl-arm NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-arm --version 6.0.13

Microsoft.NETCore.App.Runtime.linux-musl-arm64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-arm64 --version 6.0.13

Microsoft.NETCore.App.Runtime.linux-musl-x64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-musl-x64 --version 6.0.13

Microsoft.NETCore.App.Runtime.linux-x64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.linux-x64 --version 6.0.13

Microsoft.NETCore.App.Runtime.osx-arm64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.osx-arm64 --version 6.0.13

Microsoft.NETCore.App.Runtime.osx-x64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.osx-x64 --version 6.0.13

Microsoft.NETCore.App.Runtime.win-arm NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-arm --version 6.0.13

Microsoft.NETCore.App.Runtime.win-arm64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-arm64 --version 6.0.13

Microsoft.NETCore.App.Runtime.win-x64 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x64 --version 6.0.13

Microsoft.NETCore.App.Runtime.win-x86 NuGet → 6.0.13

dotnet
dotnet add package Microsoft.NETCore.App.Runtime.win-x86 --version 6.0.13

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Weakness

CWE-502: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How to prevent it
  • Architecture and Design, Implementation: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • Implementation: When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Implementation: Explicitly define a final object() to prevent deserialization.
  • Architecture and Design, Implementation: Make fields transient to protect them from deserialization. An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.
  • Implementation: Avoid having unnecessary types or gadgets (a sequence of instances and method invocations that can self-execute during the deserialization process, often found in libraries) available that can be leveraged for malicious ends. This limits the potential for unintended or unauthorized types and gadgets to be leveraged by the attacker. Add only acceptable classes to an allowlist. Note: new gadgets are constantly being discovered, so this alone is not a sufficient mitigation.
  • Architecture and Design, Implementation: Employ cryptography of the data or code for protection. However, it's important to note that it would still be client-side security. This is risky because if the client is compromised then the security implemented on the client (the cryptography) can be bypassed.
  • Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2020-1147
.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability
High Known exploited Also affects Microsoft.NETCore.App.Runtime.linux-arm
GHSA-87vj-4hqv-22p9
Microsoft Security Advisory CVE-2026-96233 - .NET and Visual Studio Denial of Service Vulnerability
High Also affects Microsoft.NETCore.App.Runtime.linux-arm
GHSA-2j93-m82w-73j2
Microsoft Security Advisory CVE-2026-96231 - .NET and Visual Studio Elevation of Privilege Vulnerability
High Also affects Microsoft.NETCore.App.Runtime.linux-arm
GHSA-w6wh-p4g7-mpj2
Microsoft Security Advisory CVE-2026-96225 - .NET and Visual Studio Elevation of Privilege Vulnerability
High Also affects Microsoft.NETCore.App.Runtime.linux-arm
GHSA-4mpw-cpwj-hxxj
Microsoft Security Advisory CVE-2026-70197 - .NET and Visual Studio Remote Code Execution Vulnerability
High Also affects Microsoft.NETCore.App.Runtime.win-arm64
GHSA-fqpq-cx42-9jmm
Microsoft Security Advisory CVE-2026-70194 - .NET and Visual Studio Security Feature Bypass Vulnerability
Medium Also affects Microsoft.NETCore.App.Runtime.linux-arm
GHSA-3rxq-g8rj-r2cf
Microsoft Security Advisory CVE-2026-69651 - .NET and Visual Studio Denial of Service Vulnerability
High Also affects Microsoft.NETCore.App.Runtime.linux-arm
GHSA-wxxw-5cvc-53j7
Microsoft Security Advisory CVE-2026-66822 - .NET and Visual Studio Information Disclosure Vulnerability
Medium Also affects Microsoft.NETCore.App.Runtime.linux-arm
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor