CVE-2024-0057 is a critical-severity (CVSS 9.8) Improper Input Validation vulnerability in NuGet.CommandLine. A fix is available for NuGet.CommandLine — see the affected versions and patch details below.
NuGet Client Security Feature Bypass Vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
NuGet.CommandLine.NETNuGet.Packaging.NETNuGet.CommandLine.NETNuGet.Packaging.NETNuGet.CommandLine.NETNuGet.Packaging.NETNuGet.CommandLine.NETNuGet.Packaging+6 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Description
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 address this vulnerability.
A security feature bypass vulnerability exists when Microsoft .NET Framework-based applications use X.509 chain building APIs but do not completely validate the X.509 certificate due to a logic flaw. An attacker could present an arbitrary untrusted certificate with malformed signatures, triggering a bug in the framework. The framework will correctly report that X.509 chain building failed, but it will return an incorrect reason code for the failure. Applications which utilize this reason code to make their own chain building trust decisions may inadvertently treat this scenario as a successful chain build. This could allow an adversary to subvert the app's typical authentication logic.
Affected software
NuGet & NuGet Packages
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.8.0 version or earlier.
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.7.0 version or earlier.
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.6.1 version or earlier.
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.4.2 version or earlier.
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.3.3 version or earlier.
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 6.0.5 version or earlier.
- Any NuGet.exe, NuGet.CommandLine, NuGet.Packaging 5.11.5 version or earlier.
.NET SDK(s)
- Any .NET SDK 6.0.126 or earlier, or 6.0.418 or earlier.
- Any .NET SDK 7.0.115 or earlier, or 7.0.312 or earlier, or 7.0.405 or earlier.
- Any .NET SDK 8.0.101 or earlier.
Patches
To fix the issue, please install the latest version of .NET 6.0, .NET 7.0 or .NET 8.0 and NuGet (NuGet.exe, NuGet.CommandLine, NuGet. Packaging versions). 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're using NuGet.exe 6.8.0 or lower, you should download and install 6.8.1 from https://dist.nuget.org/win-x86-commandline/v6.8.1/nuget.exe.
- If you're using NuGet.exe 6.7.0 or lower, you should download and install 6.7.1 from https://dist.nuget.org/win-x86-commandline/v6.7.1/nuget.exe.
- If you're using NuGet.exe 6.6.1 or lower, you should download and install 6.6.2 from https://dist.nuget.org/win-x86-commandline/v6.6.2/nuget.exe.
- If you're using NuGet.exe 6.4.2 or lower, you should download and install 6.4.3 from https://dist.nuget.org/win-x86-commandline/v6.4.3/nuget.exe.
- If you're using NuGet.exe 6.3.3 or lower, you should download and install 6.3.4 from https://dist.nuget.org/win-x86-commandline/v6.3.4/nuget.exe.
- If you're using NuGet.exe 6.0.5 or lower, you should download and install 6.0.6 from https://dist.nuget.org/win-x86-commandline/v6.0.6/nuget.exe.
- If you're using NuGet.exe 5.11.5 or lower, you should download and install 5.11.6 from https://dist.nuget.org/win-x86-commandline/v5.11.6/nuget.exe.
- If you're using .NET 8.0, you should download and install .NET 8.0.102 SDK (for Visual Studio 2022 v17.8) from https://dotnet.microsoft.com/download/dotnet-core/8.0 .
- If you're using .NET 7.0, you should download and install SDK 7.0.116 (for Visual Studio 2022 v17.4), or SDK 7.0.313 (for Visual Studio 2022 v17.6), or 7.0.406 (for Visual Studio 2022 v17.7) from https://dotnet.microsoft.com/download/dotnet-core/7.0 .
- If you're using .NET 6.0, you should download and install SDK 6.0.127 or SDK 6.0.419 (for Visual Studio 2022 v17.3) from https://dotnet.microsoft.com/download/dotnet-core/6.0 .
Other details
Announcement for this issue can be found at https://github.com/NuGet/Announcements/issues/71
MSRC details for this can be found at CVE-2024-0057 - Security Update Guide - Microsoft - NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | NuGet.CommandLine | ≥ 4.6.0&&< 5.11.6 | 5.11.6dotnet add package NuGet.CommandLine --version 5.11.6 |
| .NETNuGet | NuGet.Packaging | ≥ 4.6.0&&< 5.11.6 | 5.11.6dotnet add package NuGet.Packaging --version 5.11.6 |
| .NETNuGet | NuGet.CommandLine | ≥ 6.0.0&&< 6.0.6 | 6.0.6dotnet add package NuGet.CommandLine --version 6.0.6 |
| .NETNuGet | NuGet.Packaging | ≥ 6.0.0&&< 6.0.6 | 6.0.6dotnet add package NuGet.Packaging --version 6.0.6 |
| .NETNuGet | NuGet.CommandLine | ≥ 6.3.0&&< 6.3.4 | 6.3.4dotnet add package NuGet.CommandLine --version 6.3.4 |
| .NETNuGet | NuGet.Packaging | ≥ 6.3.0&&< 6.3.4 | 6.3.4dotnet add package NuGet.Packaging --version 6.3.4 |
Affected Products
.netmicrosoft.net frameworkmicrosoftpowershellmicrosoftvisual studio 2022microsoftDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for NuGet.CommandLine, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update NuGet.CommandLine to 5.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-0057 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The ability for an attacker to exploit this vulnerability by presenting an arbitrary untrusted certificate with malformed signatures can lead to a breach in the application's authentication logic. This loophole poses a serious threat, as it could lead to unauthorized access, data breaches, and the compromise of…
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2024-0057 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| .NET Core on Red Hat Enterprise Linux | rh-dotnet60-dotnet-0:6.0.126-1.el7_9 | RHSA-2024:0255 |
| Red Hat Enterprise Linux 8 | dotnet8.0-0:8.0.101-1.el8_9 | RHSA-2024:0150 |
| Red Hat Enterprise Linux 8 | dotnet7.0-0:7.0.115-1.el8_9 | RHSA-2024:0157 |
| Red Hat Enterprise Linux 8 | dotnet6.0-0:6.0.126-1.el8_9 | RHSA-2024:0158 |
| Red Hat Enterprise Linux 9 | dotnet7.0-0:7.0.115-1.el9_3 | RHSA-2024:0151 |
| Red Hat Enterprise Linux 9 | dotnet8.0-0:8.0.101-1.el9_3 | RHSA-2024:0152 |
| Red Hat Enterprise Linux 9 | dotnet6.0-0:6.0.126-1.el9_3 | RHSA-2024:0156 |
Frequently Asked Questions
Is CVE-2024-0057 in your dependencies?
Find it across NuGet, including transitive dependencies.