CVE-2024-43499: .NET and Visual Studio Denial of Service Vulnerability

Published Nov 1, 2024
·
Updated

.NET and Visual Studio Denial of Service Vulnerability

Other sources

.NET Core - DoS - (unbounded work factor) in NrbfDecoder component

Red Hat

Microsoft Security Advisory CVE-2024-43499 | .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 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.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/333

<a name="mitigation-factors"></a>Mitigation factors

Applications 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 software

Any .NET 9.0 application running on .NET 9.0.0.RC.2 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 9"></a>.NET 9 Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- System.Formats.Nrbf | <9.0.0 | 9.0.0

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?

1. 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. 2. 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;

.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.NetCore.App 8.0.3 [C:\Program Files\dotnet\shared\Microsoft.NetCore.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 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 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 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>.

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

CVE-2024-43499

Revisions

V1.0 (November 12, 2024): Advisory published.

Version 1.0

Last Updated 2024-11-12

GitHub

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

18 affected componentsFixes available
nuget/System.Formats.Nrbf<9.0.0
9.0.0
Microsoft PowerShell 7.5 installed on MacOS
Microsoft PowerShell 7.5 installed on Windows
Microsoft PowerShell 7.5 installed on Linux
Microsoft .NET 9.0 installed on Mac OS
Microsoft .NET 9.0 installed on Linux
Microsoft .NET 9.0 installed on Windows
Microsoft Visual Studio 2022=17.10
Microsoft Visual Studio 2022=17.6
Microsoft Visual Studio 2022=17.8
All of the following
Microsoft .NET=9.0.0
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
Microsoft Visual Studio 2022>=17.6<17.6.21
Microsoft Visual Studio 2022>=17.8<17.8.16
Microsoft Visual Studio 2022>=17.10.0<=17.10.9
Microsoft Visual Studio 2022>=17.11.0<17.11.6

Event History

Nov 1, 2024
Data Sourced
via Red Hat·07:36 PM
DescriptionSeverityAffected Software
Nov 12, 2024
CVE Published
via Microsoft·08:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionSeverity
Data Sourced
via Launchpad·10:57 PM
Description
Advisory Published
via GitHub·11:01 PM
Nov 16, 2024
Data Sourced
via Ubuntu·10:57 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·10:58 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-43499?

CVE-2024-43499 is classified as a Denial of Service (DoS) vulnerability affecting .NET Core.

2

How do I fix CVE-2024-43499?

To remediate CVE-2024-43499, update to the patched versions of Visual Studio 2022 or .NET 9.0 as specified in the security advisory.

3

Which versions of Visual Studio are affected by CVE-2024-43499?

CVE-2024-43499 affects Visual Studio 2022 versions 17.6, 17.8, and 17.11.

4

Is PowerShell 7.5 affected by CVE-2024-43499?

Yes, PowerShell 7.5 installed on Windows, MacOS, and Linux is affected by CVE-2024-43499.

5

What component of .NET Core is vulnerable in CVE-2024-43499?

The vulnerability in CVE-2024-43499 exists in the NrbfDecoder component of .NET Core.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203