Microsoft Security Advisory CVE-2024-35264 | .NET Remote Code Execution Vulnerability

[rbhanda]

Microsoft Security Advisory CVE-2024-35264 | .NET Remote Code Execution Vulnerability

Executive summary

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

A Vulnerability exists in ASP.NET Core 8 where Data Corruption in Kestrel HTTP/3 can result in remote code execution.

Note: HTTP/3 is experimental in .NET 6.0. If you are on .NET 6.0 and using HTTP/3, please upgrade to .NET 8.0.7

Announcement

Announcement for this issue can be found at dotnet/announcements#314

Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

Affected software

• Any .NET 8.0 application running on .NET 8.0.6 or earlier.

Affected Packages

The vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below

ASP.NET 8

Package name	Affected version	Patched version
Microsoft.AspNetCore.App.Runtime.linux-arm	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.linux-arm64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.linux-musl-arm	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.linux-musl-arm64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.linux-musl-x64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.linux-x64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.osx-arm64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.osx-x64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.win-arm	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.win-arm64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.win-x64	>=8.0.0, <= 8.0.6	8.0.7
Microsoft.AspNetCore.App.Runtime.win-x86	>=8.0.0, <= 8.0.6	8.0.7

Advisory FAQ

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.

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 --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.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.

.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 7.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.

Acknowledgement

Radek Zikmund of Microsoft Corporation

External Links

CVE-2024-35264

Revisions

V1.0 (July 09, 2024): Advisory published.

Version 1.0

Last Updated 2024-07-09

[wenz]

I'd like to suggest to change "To fix the issue please install the latest version of .NET 8.0 or .NET 7.0 or .NET 6.0." to "To fix the issue please install the latest version of .NET 8.0", since it is my understanding that .NET 6 and 7 won't receive a fix for this?

[Mart-Bogdan]

Description mentions Kestrel, so do it affect only server part of HTTP/3 or HTTP client is also wulnerable?

So if reverse proxy is for SSL termination and HTTP/3, then this CVE won't be exploitable?