February 13th, 2024

.NET February 2024 Updates – .NET 8.0.2, 7.0.16, .NET 6.0.27

Rahul Bhandari (MSFT)
Senior Program Manager

Today, we are releasing the .NET February 2024 Updates. These updates contain security and non-security improvements. Your app may be vulnerable if you have not deployed a recent .NET update.

You can download 8.0.2, 7.0.16 and, 6.0.27 versions for Windows, macOS, and Linux, for x86, x64, Arm32, and Arm64.

Windows Package Manager CLI (winget)

You can now install .NET updates using the Windows Package Manager CLI (winget):

  • To install the .NET 8 runtime: winget install dotnet-runtime-8
  • To install the .NET 8 SDK: winget install dotnet-sdk-8
  • To update an existing installation: winget upgrade

See Install with Windows Package Manager (winget) for more information.

Improvements

Security

CVE-2024-21386 – .NET Denial of Service Vulnerability

Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET 6.0, ASP.NET 7.0 and, ASP.NET 8.0 . This advisory also provides guidance on what developers can do to update their applications to address this vulnerability.

A vulnerability exists in ASP.NET applications using SignalR where a malicious client can result in a denial-of-service.

CVE-2024-21404- .NET Denial of Service Vulnerability

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0, .NET 7.0 and .NET 8.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

A denial-of-service vulnerability exists in .NET with OpenSSL support when parsing X509 certificates.

Visual Studio

See release notes for Visual Studio compatibility for .NET 8.0, .NET 7.0 and, .NET 6.0.

Author

Rahul Bhandari (MSFT)
Senior Program Manager

I am a Program Manager on .NET team. I specializes in .NET release processes. University of Florida Alumnus.

1 comment

Discussion is closed. Login to edit/delete existing comments.

  • Brendan

    Your link to CVE-2024-21404 is broken.
    The URL is going to CVE-2023-21404 instead of CVE-2024-21404