GHSA-6x36-qxmj-rv4p .NET Denial of Service Vulnerability
Microsoft Security Advisory CVE-2024-43499 | .NET Denial of Service Vulnerability<a name="executive-summary"></a>Executive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in .NET 9.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.The NrbfDecoder component in .NET 9 contains a denial of service vulnerability due to incorrect input validation.AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/333<a name="mitigation-factors"></a>Mitigation factorsApplications that do not use the NrbfDecoder component are not affected by this vulnerability. By default, .NET console apps and web apps do not reference this component.<a name="affected-software"></a>Affected softwareAny .NET 9.0 application running on .NET 9.0.0.RC.2 or earlier.<a name="affected-packages"></a>Affected PackagesThe vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below<a name=".NET 9"></a>.NET 9Package name | Affected version | Patched version
------------ | ---------------- | -------------------------
[System.Formats.Nrbf](https://www.nuget.org/packages/System.Formats.Nrbf)               |  <9.0.0 | 9.0.0Advisory 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](#affected-packages) or [affected packages](#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 9.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 your application references the vulnerable package, update the package reference to the patched version.Note: You may need to take both actions. Upgrading to 9.0 GA is not by itself sufficient to resolve the vulnerability, since you could still be pulling in the vulnerable package by reference.If you have .NET 8.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;If you're using .NET 9.0, you should download and install .NET 9.0  Runtime or .NET 9.0.100 SDK (for Visual Studio 2022 v17.12 latest Preview) from https://dotnet.microsoft.com/download/dotnet-core/9.0.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](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 9.0 or .NET 8.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>.SupportYou 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.DisclaimerThe 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-2024-43499]( https://www.cve.org/CVERecord?id=CVE-2024-43499)RevisionsV1.0 (November 12, 2024): Advisory published._Version 1.0__Last Updated 2024-11-12_
CVSS v4.0 score: 8.7
CVSS v3.1 score: 7.5