GHSA-447r-wph3-92pm BIT-dotnet-2024-38095 BIT-dotnet-sdk-2024-38095 CVE-2024-38095
Microsoft Security Advisory CVE-2024-38095 | .NET Denial of Service Vulnerability
- Severity
- 0.0 / 10
- High · CVSS 4.0
- Exploit chance (EPSS)
- 2.74%
- Chance of exploitation in the next 30 days. Higher than 86.17% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-20 Improper Input Validation
- Fix
- Available
- 13 packages have a fixed version
Description
Microsoft Security Advisory CVE-2024-38095 | .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 and .NET 8.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A Vulnerability exists when System.Formats.Asn1 in .NET parses an X.509 certificate or collection of certificates, a malicious certificate can result in excessive CPU consumption on all platforms result in Denial of Service.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/312
<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.31 or earlier.
- Any .NET 8.0 application running on .NET 8.0.6 or earlier.
<a name="affected-packages"></a>Affected Packages
The vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below
<a name=".NET 6"></a>.NET 6
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.NetCore.App.Runtime.linux-arm | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.linux-arm64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.linux-musl-arm | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.linux-musl-arm64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.linux-musl-x64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.linux-x64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.osx-arm64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.osx-x64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.win-arm | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.win-arm64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.win-x64 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| Microsoft.NetCore.App.Runtime.win-x86 | >=6.0.0, <= 6.0.31 | 6.0.32 |
| System.Formats.Asn1 | >=5.0.0-preview.7.20364.11 | 6.0.1 |
<a name=".NET 8"></a>.NET 8
| Package name | Affected version | Patched version |
|---|---|---|
| Microsoft.NetCore.App.Runtime.linux-arm | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.linux-arm64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.linux-musl-arm | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.linux-musl-arm64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.linux-musl-x64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.linux-x64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.osx-arm64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.osx-x64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.win-arm | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.win-arm64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.win-x64 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| Microsoft.NetCore.App.Runtime.win-x86 | >=8.0.0, <= 8.0.6 | 8.0.7 |
| System.Formats.Asn1 | <=6.0.0, >=7.0.0-preview.1.22076.8 | 8.0.1 |
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 or affected packages, 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 8.0 or .NET 7.0 or .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 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: 8.0.200
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: 8.0.3
Commit: 8473146e7d
.NET Core SDKs installed:
8.0.200 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspAspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspAspNetCore.App]
Microsoft.AspNetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.WindowsDesktop.App 8.0.3 [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 8.0, you should download and install .NET 8.0.7 Runtime or .NET 8.0.107 SDK (for Visual Studio 2022 v17.8) from https://dotnet.microsoft.com/download/dotnet-core/8.0.
- If you're using .NET 6.0, you should download and install Runtime 6.0.32 or SDK 6.0.132 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
.NET 6.0 and .NET 8.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 8.0 or .NET 6.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 (July 09, 2024): Advisory published.
Version 1.0
Last Updated 2024-07-09
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.NetCore.App.Runtime.linux-arm NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-arm --version 8.0.7
Microsoft.NetCore.App.Runtime.linux-arm64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-arm64 --version 8.0.7
Microsoft.NetCore.App.Runtime.linux-musl-arm NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-musl-arm --version 8.0.7
Microsoft.NetCore.App.Runtime.linux-musl-arm64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-musl-arm64 --version 8.0.7
Microsoft.NetCore.App.Runtime.linux-musl-x64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-musl-x64 --version 8.0.7
Microsoft.NetCore.App.Runtime.linux-x64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.linux-x64 --version 8.0.7
Microsoft.NetCore.App.Runtime.osx-arm64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.osx-arm64 --version 8.0.7
Microsoft.NetCore.App.Runtime.osx-x64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.osx-x64 --version 8.0.7
Microsoft.NetCore.App.Runtime.win-arm NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-arm --version 8.0.7
Microsoft.NetCore.App.Runtime.win-arm64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-arm64 --version 8.0.7
Microsoft.NetCore.App.Runtime.win-x64 NuGet → 8.0.7
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-x64 --version 8.0.7
Microsoft.NetCore.App.Runtime.win-x86 NuGet → 6.0.32
- dotnet
dotnet add package Microsoft.NetCore.App.Runtime.win-x86 --version 6.0.32
System.Formats.Asn1 NuGet → 6.0.1
- dotnet
dotnet add package System.Formats.Asn1 --version 6.0.1
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- None
- User interaction
- None
- Confidentiality (vulnerable system)
- None
- Integrity (vulnerable system)
- None
- Availability (vulnerable system)
- High
- Confidentiality (subsequent systems)
- None
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
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-20: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How to prevent it
- Architecture and Design: Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build "recognizers" for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses. [REF-1109] [REF-1110] [REF-1111]
- Architecture and Design: Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Architecture and Design, Implementation: Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
- Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server. Even though client-side checks provide minimal benefits with respect to server-side security, they are still useful. First, they can support intrusion detection. If the server receives input that should have been rejected by the client, then it may be an indication of an attack. Second, client-side error-checking can provide helpful feedback to the user about the expectations for valid input. Third, there may be a reduction in server-side processing time for accidental input errors, although this is typically a small savings.
- Implementation: When your application combines data from multiple sources, perform the validation after the sources have been combined. The individual data elements may pass the validation step but violate the intended restrictions after they have been combined.
- Implementation: Be especially careful to validate all input when invoking code that crosses language boundaries, such as from an interpreted language to native code. This could create an unexpected interaction between the language boundaries. Ensure that you are not violating any of the expectations of the language with which you are interfacing. For example, even though Java may not be susceptible to buffer overflows, providing a large argument in a call to native code might trigger an overflow.
- Implementation: Directly convert your input type into the expected data type, such as using a conversion function that translates a string into a number. After converting to the expected data type, ensure that the input's values fall within the expected range of allowable values and that multi-field consistencies are maintained.
- Implementation: Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180, CWE-181). Make sure that your application does not inadvertently decode the same input twice (CWE-174). Such errors could be used to bypass allowlist schemes by introducing dangerous inputs after they have been checked. Use libraries such as the OWASP ESAPI Canonicalization control. Consider performing repeated canonicalization until your input does not change any more. This will avoid double-decoding and similar scenarios, but it might inadvertently modify inputs that are allowed to contain properly-encoded dangerous content.
- Implementation: When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| CVE-2020-1147 .NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability | High Known exploited | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| 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.linux-arm |
| GHSA-2j93-m82w-73j2 Microsoft Security Advisory CVE-2026-96231 - .NET and Visual Studio Elevation of Privilege Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-w6wh-p4g7-mpj2 Microsoft Security Advisory CVE-2026-96225 - .NET and Visual Studio Elevation of Privilege Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| 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-fqpq-cx42-9jmm Microsoft Security Advisory CVE-2026-70194 - .NET and Visual Studio Security Feature Bypass Vulnerability | Medium | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-3rxq-g8rj-r2cf Microsoft Security Advisory CVE-2026-69651 - .NET and Visual Studio Denial of Service Vulnerability | High | Also affects Microsoft.NETCore.App.Runtime.linux-arm |
| GHSA-wxxw-5cvc-53j7 Microsoft Security Advisory CVE-2026-66822 - .NET and Visual Studio Information Disclosure Vulnerability | Medium | Also affects Microsoft.NETCore.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