Closed rbhanda closed 2 months ago
Tagging subscribers to this area: @dotnet/area-meta See info in area-owners.md if you want to be subscribed.
Although all publicly available information lists only .NET 7.0 and 8.0 versions as affected (and some Visual Studio versions), somehow this CVE is now plastered all over the listed NuGet package versions e.g. for .NET 6.0 (see e.g., here) and various scanners including e.g., Microsoft Defender for Containers are now reporting this CVE against the .NET 6.0.30 runtime (e.g., for Microsoft-issued images like mcr.microsoft.com/dotnet/runtime:6.0.30-jammy-amd64
we use, among others), i.e., the latest one, so as per the "How do I fix the issue?" section.
Who thought, that listing everything "at and below 7.0.18", instead of e.g., "between 7.0.0-preview.1 and 7.0.18" is a good idea?
Unless .NET 6.0 is also affected, but somehow not mentioned and/or not patched (although a patch release for .NET 6.0 was released at the same time as for 7.0 and 8.0).
Although all publicly available information lists only .NET 7.0 and 8.0 versions as affected (and some Visual Studio versions), somehow this CVE is now plastered all over the listed NuGet package versions e.g. for .NET 6.0 (see e.g., here) and various scanners including e.g., Microsoft Defender for Containers are now reporting this CVE against the .NET 6.0.30 runtime (e.g., for Microsoft-issued images like
mcr.microsoft.com/dotnet/runtime:6.0.30-jammy-amd64
we use, among others), i.e., the latest one, so as per the "How do I fix the issue?" section. Who thought, that listing everything "at and below 7.0.18", instead of e.g., "between 7.0.0-preview.1 and 7.0.18" is a good idea? Unless .NET 6.0 is also affected, but somehow not mentioned and/or not patched (although a patch release for .NET 6.0 was released at the same time as for 7.0 and 8.0).
hI @hilari0n , my sincere apologies for this. We have corrected our advisories to reflect correct versions of .NET 7 and .NET 8 impacted
is the PR/commit fixing this issue available? I'm interested how a buffer overflow could sneak into managed/safe code.
@fowl2 Perhaps it's this commit: https://github.com/dotnet/runtime/commit/06650b7f1bd158c6c270e6f627a8c90d8eee3836.
@fowl2 Perhaps it's this commit: 06650b7.
The CVE only mentions 7.0 and 8.0 as affected, while the cause of the commit seems to be #98841, which mentions, that the problem is there since 6.0 (which is not mentioned in the CVE) and does not describe it as a security concern at all. So either this is it, but 6.0 was not yet fixed, or this is not it.
Microsoft Security Advisory CVE-2024-30045 | .NET Remote code Execution Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A Remote Code Execution vulnerability exists in .NET 7.0 and .NET 8.0 where a stack buffer overrun occurs in .NET Double Parse routine.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/307
Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
Affected software
Affected Packages
The vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below
.NET 7
.NET 8
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?
dotnet --info
command. You will see output like the following;.NET 7.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 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.
External Links
CVE-2024-30045
Revisions
V1.0 (May 14, 2024): Advisory published.
Version 1.0
Last Updated 2024-05-14