What is CVE-2024-0057?

CVE-2024-0057 is a critical-severity security vulnerability in NuGet.CommandLine (nuget), affecting versions >= 4.6.0, < 5.11.6. It is fixed in 5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1.

How severe is CVE-2024-0057?

CVE-2024-0057 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2024-0057?

NuGet.CommandLine (nuget) versions >= 4.6.0, = 4.6.0, < 5.11.6.

Is there a fix for CVE-2024-0057?

Yes. CVE-2024-0057 is fixed in 5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1. Upgrade to this version or later.

Is CVE-2024-0057 exploitable, and should I be worried?

Whether CVE-2024-0057 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-0057 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-0057?

Upgrade: NuGet.CommandLine to 5.11.6 or later, NuGet.Packaging to 5.11.6 or later, NuGet.CommandLine to 6.0.6 or later, NuGet.Packaging to 6.0.6 or later, NuGet.CommandLine to 6.3.4 or later, NuGet.Packaging to 6.3.4 or later, NuGet.CommandLine to 6.4.3 or later, NuGet.Packaging to 6.4.3 or later, NuGet.CommandLine to 6.6.2 or later, NuGet.Packaging to 6.6.2 or later, NuGet.CommandLine to 6.7.1 or later, NuGet.Packaging to 6.7.1 or later, NuGet.CommandLine to 6.8.1 or later, NuGet.Packaging to 6.8.1 or later.

CVE-2024-0057 in NuGet.CommandLine

Q: How severe is CVE-2024-0057?

CVE-2024-0057 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2024-0057?

NuGet.CommandLine (nuget) versions >= 4.6.0, = 4.6.0, < 5.11.6.

Q: Is there a fix for CVE-2024-0057?

Yes. CVE-2024-0057 is fixed in 5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1. Upgrade to this version or later.

Q: Is CVE-2024-0057 exploitable, and should I be worried?

Whether CVE-2024-0057 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-0057 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-0057?

Upgrade: NuGet.CommandLine to 5.11.6 or later, NuGet.Packaging to 5.11.6 or later, NuGet.CommandLine to 6.0.6 or later, NuGet.Packaging to 6.0.6 or later, NuGet.CommandLine to 6.3.4 or later, NuGet.Packaging to 6.3.4 or later, NuGet.CommandLine to 6.4.3 or later, NuGet.Packaging to 6.4.3 or later, NuGet.CommandLine to 6.6.2 or later, NuGet.Packaging to 6.6.2 or later, NuGet.CommandLine to 6.7.1 or later, NuGet.Packaging to 6.7.1 or later, NuGet.CommandLine to 6.8.1 or later, NuGet.Packaging to 6.8.1 or later.

Summary

NuGet Client Security Feature Bypass Vulnerability

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.

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

Impact

CVE-2024-0057 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1); upgrading removes the vulnerable code path.

Affected versions

NuGet.CommandLine (>= 4.6.0, < 5.11.6) NuGet.Packaging (>= 4.6.0, < 5.11.6) NuGet.CommandLine (>= 6.0.0, < 6.0.6) NuGet.Packaging (>= 6.0.0, < 6.0.6) NuGet.CommandLine (>= 6.3.0, < 6.3.4) NuGet.Packaging (>= 6.3.0, < 6.3.4) NuGet.CommandLine (>= 6.4.0, < 6.4.3) NuGet.Packaging (>= 6.4.0, < 6.4.3) NuGet.CommandLine (>= 6.6.0, < 6.6.2) NuGet.Packaging (>= 6.6.0, < 6.6.2) NuGet.CommandLine (= 6.7.0) NuGet.Packaging (= 6.7.0) NuGet.CommandLine (= 6.8.0) NuGet.Packaging (= 6.8.0)

Security releases

NuGet.CommandLine → 5.11.6 (nuget) NuGet.Packaging → 5.11.6 (nuget) NuGet.CommandLine → 6.0.6 (nuget) NuGet.Packaging → 6.0.6 (nuget) NuGet.CommandLine → 6.3.4 (nuget) NuGet.Packaging → 6.3.4 (nuget) NuGet.CommandLine → 6.4.3 (nuget) NuGet.Packaging → 6.4.3 (nuget) NuGet.CommandLine → 6.6.2 (nuget) NuGet.Packaging → 6.6.2 (nuget) NuGet.CommandLine → 6.7.1 (nuget) NuGet.Packaging → 6.7.1 (nuget) NuGet.CommandLine → 6.8.1 (nuget) NuGet.Packaging → 6.8.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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 .

Frequently Asked Questions

What is CVE-2024-0057? CVE-2024-0057 is a critical-severity security vulnerability in NuGet.CommandLine (nuget), affecting versions >= 4.6.0, < 5.11.6. It is fixed in 5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1.
How severe is CVE-2024-0057? CVE-2024-0057 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2024-0057?
- NuGet.CommandLine (nuget) (versions >= 4.6.0, < 5.11.6)
- NuGet.Packaging (nuget) (versions >= 4.6.0, < 5.11.6)
Is there a fix for CVE-2024-0057? Yes. CVE-2024-0057 is fixed in 5.11.6, 6.0.6, 6.3.4, 6.4.3, 6.6.2, 6.7.1, 6.8.1. Upgrade to this version or later.
Is CVE-2024-0057 exploitable, and should I be worried? Whether CVE-2024-0057 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-0057 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-0057?
- Upgrade NuGet.CommandLine to 5.11.6 or later
- Upgrade NuGet.Packaging to 5.11.6 or later
- Upgrade NuGet.CommandLine to 6.0.6 or later
- Upgrade NuGet.Packaging to 6.0.6 or later
- Upgrade NuGet.CommandLine to 6.3.4 or later
- Upgrade NuGet.Packaging to 6.3.4 or later
- Upgrade NuGet.CommandLine to 6.4.3 or later
- Upgrade NuGet.Packaging to 6.4.3 or later
- Upgrade NuGet.CommandLine to 6.6.2 or later
- Upgrade NuGet.Packaging to 6.6.2 or later
- Upgrade NuGet.CommandLine to 6.7.1 or later
- Upgrade NuGet.Packaging to 6.7.1 or later
- Upgrade NuGet.CommandLine to 6.8.1 or later
- Upgrade NuGet.Packaging to 6.8.1 or later

Other vulnerabilities in NuGet.CommandLine

CVE-IDSeverityPackage summary

GHSA-G4VJ-CJJJ-V7HGLowNuGet.Packaging: Defense in Depth update for NuGet Client CVE-2023-29337HighMicrosoft.Build.NuGetSdkResolver: NuGet Client Remote Code Execution Vulnerability CVE-2022-41032HighNuGet.Commands: NuGet Elevation of Privilege Vulnerability CVE-2022-30184MediumNuGet.Commands: Potential leak of NuGet.org API key