GHSA-p57v-gv7q-4xfm BIT-dotnet-2023-38178 BIT-dotnet-sdk-2023-38178 CVE-2023-38178
.NET Denial of Service Vulnerability
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 2.59%
- Chance of exploitation in the next 30 days. Higher than 85.30% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 8 packages have a fixed version
Description
Microsoft Security Advisory CVE-2023-38178: .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 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 https://github.com/dotnet/announcements/issues/268
<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 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.
<a name=".NET 7"></a>.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 |
<a name=".NET 6"></a>.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
<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 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
libmsquicto 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 --infocommand. 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 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
Revisions
V1.0 (August 08, 2023): Advisory published.
Version 1.0
Last Updated 2023-08-08
Affected versions
NuGet
| Package | Vulnerable | Fixed in |
|---|---|---|
| Microsoft.AspNetCore.App.Runtime.win-arm | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.NetCore.App.Runtime.win-arm | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.NetCore.App.Runtime.win-arm64 | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.NetCore.App.Runtime.win-x64 | >= 7.0.0, < 7.0.10 |
7.0.10 |
| Microsoft.NetCore.App.Runtime.win-x86 | >= 7.0.0, < 7.0.10 |
7.0.10 |
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.AspNetCore.App.Runtime.win-arm NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm --version 7.0.10
Microsoft.AspNetCore.App.Runtime.win-arm64 NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm64 --version 7.0.10
Microsoft.AspNetCore.App.Runtime.win-x64 NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 7.0.10
Microsoft.AspNetCore.App.Runtime.win-x86 NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x86 --version 7.0.10
Microsoft.NetCore.App.Runtime.win-arm NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-arm --version 7.0.10
Microsoft.NetCore.App.Runtime.win-arm64 NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-arm64 --version 7.0.10
Microsoft.NetCore.App.Runtime.win-x64 NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-x64 --version 7.0.10
Microsoft.NetCore.App.Runtime.win-x86 NuGet → 7.0.10
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-x86 --version 7.0.10
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-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-vmch-3w2x-vhgq .NET Denial of Service Vulnerability | High Known exploited | Also affects Microsoft.AspNetCore.App.Runtime.win-arm64 |
| CVE-2020-1147 .NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability | High Known exploited | Also affects Microsoft.NETCore.App.Runtime.win-arm |
| GHSA-f4g7-52wc-p8x7 Microsoft Security Advisory CVE-2026-96236 - ASP.NET Core Denial of Service Vulnerability | High | Also affects Microsoft.AspNetCore.App.Runtime.win-arm64 |
| 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.win-arm |
| GHSA-rv87-ccxw-8ggf Microsoft Security Advisory CVE-2026-88092 - ASP.NET Core Security Feature Bypass Vulnerability | Critical | Also affects Microsoft.AspNetCore.App.Runtime.win-arm64 |
| 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-57xr-hfxx-jw5x Microsoft Security Advisory CVE-2026-70196 - ASP.NET Core Denial of Service Vulnerability | Medium | Also affects Microsoft.AspNetCore.App.Runtime.win-arm |
| GHSA-fpq8-4vhr-rcxx Microsoft Security Advisory CVE-2026-70188 - ASP.NET Core Security Feature Bypass Vulnerability | Critical | Also affects Microsoft.AspNetCore.App.Runtime.win-arm64 |
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