Microsoft Security Advisory CVE-2023-38178: .NET Denial of Service Vulnerability****Executive summary

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

A vulnerability exists in .NET Kestrel where a malicious client can bypass QUIC stream limit in HTTP/3 in both ASP.NET and .NET runtimes resulting in denial of service.

Announcement

Announcement for this issue can be found at dotnet/announcements#268

Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

Affected software

• Any .NET 7.0 application running on .NET 7.0.9 or earlier.

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

.NET 7

Package name

Affected version

Patched version

Microsoft.AspNetCore.App.Runtime.win-arm64

>= 7.0.0, <= 7.0.9

7.0.10

Microsoft.AspNetCore.App.Runtime.win-arm

>= 7.0.0, <= 7.0.9

7.0.10

Microsoft.AspNetCore.App.Runtime.win-x64

>= 7.0.0, <= 7.0.9

7.0.10

Microsoft.AspNetCore.App.Runtime.win-x86

>= 7.0.0, <= 7.0.9

7.0.10

[Microsoft.NetCore.App.Runtime.win-arm](https://www.nuget.org/packages/ Microsoft.NetCore.App.Runtime.win-arm)

>= 7.0.0, <= 7.0.9

7.0.10

Microsoft.NetCore.App.Runtime.win-arm

>= 7.0.0, <= 7.0.9

7.0.10

Microsoft.NetCore.App.Runtime.win-x86

>= 7.0.0, <= 7.0.9

7.0.10

Microsoft.NetCore.App.Runtime.win-x64

>= 7.0.0, <= 7.0.9

7.0.10

.NET 6

.NET 6 included HTTP/3 support as a preview feature , which requires specific opt-in code. If you are using HTTP/3 in .NET 6 you must update your application to .NET 7, where the feature is supported, to fix the vulnerability. Future versions of .NET will disable the preview feature entirely.

Advisory FAQ****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.

How do I fix the issue?

• To fix the issue please install the latest version of .NET 7.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.

• To fix this issue on Linux, please update libmsquic to 2.2+

• If you are using one of the affected packages, please update to the patched version listed above.

• If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the dotnet --info command. You will see output like the following;

  .NET Core SDK (reflecting any global.json):

  Version: 7.0.400 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: 7.0.10 Commit: 8473146e7d

  .NET Core SDKs installed:

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

  .NET Core runtimes installed:

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

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

• If you’re using .NET 7.0, you should download and install Runtime 7.0.10 or SDK 7.0.700 (for Visual Studio 2022 v17.7) from https://dotnet.microsoft.com/download/dotnet-core/6.0.

.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 [email protected]. 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-38178

Revisions

V1.0 (August 08, 2023): Advisory published.

Version 1.0

Last Updated 2023-08-08

References

• GHSA-p57v-gv7q-4xfm
• https://nvd.nist.gov/vuln/detail/CVE-2023-38178
• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-38178