GHSA-cw98-9j8w-wxv9 BIT-dotnet-2022-24464 BIT-dotnet-sdk-2022-24464 CVE-2022-24464
.NET Denial of Service Vulnerability
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 3.55%
- Chance of exploitation in the next 30 days. Higher than 89.31% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 12 packages have a fixed version
Description
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 5.0, and .NET CORE 3.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Microsoft is aware of a Denial of Service vulnerability, which exists in .NET 6.0, .NET 5.0, and .NET CORE 3.1 when parsing certain types of http form requests.
Affected Software
- Any .NET 6.0 application running on .NET 6.0.2 or lower
- Any .NET 5.0 application running on .NET 5.0.14 or lower
- Any .NET Core 3.1 application running on .NET Core 3.1.22 or lower
Patches
To fix the issue, please install the latest version of .NET 6.0 or .NET 5.0 or .NET Core 3.1.. 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're using .NET Core 6.0, you should download and install Runtime 6.0.3 or SDK 6.0.201 (for Visual Studio 2022 v17.1) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
-
If you're using .NET 5.0, you should download and install Runtime 5.0.15 or SDK 5.0.406 (for Visual Studio 2019 v16.11) or SDK 5.0.212 (for Visual Studio 2011 v16.9) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
-
If you're using .NET Core 3.1, you should download and install Runtime 3.1.23 or SDK 3.1.417 (for Visual Studio 2019 v16.7.26) from https://dotnet.microsoft.com/download/dotnet-core/5.0. .NET 6.0 and .NET 5.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.
.NET 6.0 and .NET 5.0 and, .NET Core 3.1 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.
Other Details
- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/212
- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/40598
- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/ CVE-2022-24464
Affected versions
NuGet
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.linux-arm NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 3.1.23
Microsoft.AspNetCore.App.Runtime.linux-arm64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.linux-musl-arm NuGet → 5.0.15
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm --version 5.0.15
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.linux-musl-x64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-x64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.linux-x64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.osx-arm64 NuGet → 6.0.3
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.osx-arm64 --version 6.0.3
Microsoft.AspNetCore.App.Runtime.osx-x64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.osx-x64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.win-arm NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm --version 3.1.23
Microsoft.AspNetCore.App.Runtime.win-arm64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.win-x64 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 3.1.23
Microsoft.AspNetCore.App.Runtime.win-x86 NuGet → 3.1.23
- dotnet
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x86 --version 3.1.23
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
Other links
- github.com/dotnet/aspnetcore/security/advisories/GHSA-cw98-9j8w-wxv9
- github.com/dotnet/announcements/issues/212
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4TOGT…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CIJGC…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQLM7…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MRGSP…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OS2Q4…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZXEQ3…
- msrc.microsoft.com/update-guide/vulnerability/CVE-2022-24464
- portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-24464
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 |
| GHSA-f4g7-52wc-p8x7 Microsoft Security Advisory CVE-2026-96236 - ASP.NET Core Denial of Service Vulnerability | High | Also affects Microsoft.AspNetCore.App.Runtime.linux-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.linux-arm |
| GHSA-57xr-hfxx-jw5x Microsoft Security Advisory CVE-2026-70196 - ASP.NET Core Denial of Service Vulnerability | Medium | Also affects Microsoft.AspNetCore.App.Runtime.linux-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.linux-arm |
| GHSA-mf4x-w4gh-4656 Microsoft Security Advisory CVE-2026-70186 - ASP.NET Core Denial of Service Vulnerability | High | Also affects Microsoft.AspNetCore.App.Runtime.linux-arm |
| GHSA-494h-xx7x-5frh Microsoft Security Advisory CVE-2026-70183 - ASP.NET Core Security Feature Bypass Vulnerability | High | Also affects Microsoft.AspNetCore.App.Runtime.linux-arm |
| GHSA-w5qq-qrpp-rf4c Microsoft Security Advisory CVE-2026-70181 - ASP.NET Core Denial of Service Vulnerability | High | Also affects Microsoft.AspNetCore.App.Runtime.linux-arm |
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