.NET Denial of Service Vulnerability

Affecting Microsoft.NetCore.App.Runtime.linux-arm package on NuGet

Context / Overview

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 nameAffected versionPatched version
Microsoft.NetCore.App.Runtime.linux-arm>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.linux-arm64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.linux-musl-arm>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.linux-musl-arm64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.linux-musl-x64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.linux-x64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.osx-arm64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.osx-x64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.win-arm>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.win-arm64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.win-x64>= 6.0.0, <= 6.0.126.0.13
Microsoft.NetCore.App.Runtime.win-x86>= 6.0.0, <= 6.0.126.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

Jit Recommended Tools

OSV-Scanner

Objective: Dependency check (SCA)

Description: OSV-Scanner provides an officially supported frontend to the OSV database that connects a project’s list of dependencies with the vulnerabilities that affect them. Since the OSV.dev database is open source and distributed, it has several benefits in comparison with closed source advisory databases and scanners:

Vulnerability Layer - SCA

SCA Dependency Check is one of the important tools used to identify vulnerabilities in open-source components used in software applications. However, it primarily focuses on identifying vulnerabilities in the dependency layer of the software application. In contrast, code vulnerability layer analysis is focused on identifying vulnerabilities in the source code of the application itself, rather than the dependencies it uses. It typically involves analyzing the source code to identify security issues such as buffer overflows, injection vulnerabilities, and authentication issues, among others. While SCA Dependency Check is an important tool in identifying vulnerabilities in open-source dependencies, it may not be sufficient to ensure the overall security of the software application. To ensure comprehensive security, it is important to also perform code vulnerability layer analysis to identify vulnerabilities in the source code of the application. Incorporating both SCA Dependency Check and code vulnerability layer analysis into the software development lifecycle can help ensure that vulnerabilities are identified and remediated at both the dependency and code layers of the application. This can help prevent security issues from being introduced into the final product and improve the overall security posture of the software application.

References & Sources

Similar Vulnerabilities

;