Quick answers
- Is CVE-2022-24464 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-24464 being exploited in the wild.
- How severe is CVE-2022-24464?
- High severity, with a CVSS score of 7.5, published 21 October 2022.
- Which products and versions are affected?
- Microsoft .NET Core 3.1.0 to 3.1.22; Microsoft Visual Studio 2019 16.0 to 16.11; Microsoft Visual Studio 2022 17.0 to 17.1; Microsoft.AspNetCore.App.Runtime.linux-arm (NuGet) ECOSYSTEM:introduced=3.0.0,fixed=3.1.23; and 11 more.
- Is there a fix for CVE-2022-24464?
- Yes. Microsoft.AspNetCore.App.Runtime.linux-arm (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.linux-arm64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.linux-musl-arm (NuGet): upgrade to 5.0.15 or later; Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.linux-musl-x64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.linux-x64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.osx-arm64 (NuGet): upgrade to 6.0.3 or later; Microsoft.AspNetCore.App.Runtime.osx-x64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.win-arm (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet): upgrade to 3.1.23 or later; Microsoft.AspNetCore.App.Runtime.win-x86 (NuGet): upgrade to 3.1.23 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-24464 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-24464?
- Check whether you run Microsoft .NET Core, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Microsoft.AspNetCore.App.Runtime.linux-arm (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.linux-arm64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.linux-musl-arm (NuGet): upgrade to 5.0.15 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm --version 5.0.15 - Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.linux-musl-x64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-musl-x64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.linux-x64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.linux-x64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.osx-arm64 (NuGet): upgrade to 6.0.3 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.osx-arm64 --version 6.0.3 - Microsoft.AspNetCore.App.Runtime.osx-x64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.osx-x64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.win-arm (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.win-arm64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.win-arm64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.win-x64 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x64 --version 3.1.23 - Microsoft.AspNetCore.App.Runtime.win-x86 (NuGet): upgrade to 3.1.23 or later
dotnet add package Microsoft.AspNetCore.App.Runtime.win-x86 --version 3.1.23
Technical details
A denial-of-service vulnerability exists in .NET 6.0, .NET 5.0, and .NET Core 3.1 due to improper handling of specific HTTP form requests. The root cause is related to uncontrolled resource consumption (CWE-400) during the parsing of these requests. A remote, unauthenticated attacker can exploit this by sending a malicious HTTP request to a vulnerable application, leading to a crash or exhaustion of resources. This affects applications built on the impacted .NET runtimes and developers using specific versions of Visual Studio. Microsoft has released patches in .NET 6.0.3, 5.0.15, and 3.1.23 to address the issue.
Affected products
- Microsoft .NET 5.0.0 to 5.0.14, 6.0.0 to 6.0.2
- Microsoft .NET Core 3.1.0 to 3.1.22
- Microsoft Visual Studio 2019 16.0 to 16.11
- Microsoft Visual Studio 2022 17.0 to 17.1
Identifiers
- CVE-2022-24464
- GHSA-cw98-9j8w-wxv9
Timeline
- 2022-03-08: advisory: Initial advisory published by Microsoft
- 2022-03-08: patched: Fixed versions released (6.0.3, 5.0.15, 3.1.23)
- 2022-10-21: disclosed: GitHub Advisory published
References
- https://github.com/dotnet/aspnetcore/security/advisories/GHSA-cw98-9j8w-wxv9
- https://github.com/dotnet/announcements/issues/212
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-24464
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-24464
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4TOGTZ2ZWDH662ZNFFSZVL3M5AJXV6JF