CVE-2024-0057: NuGet Client Security Feature Bypass Vulnerability

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 2.8%, percentile 86: FIRST’s model estimates a 2.8% chance of exploitation activity in the next 30 days, higher than 86% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes NuGet.CommandLine (NuGet) >= 4.6.0, < 5.11.6, fixed in 5.11.6; NuGet.Packaging (NuGet) >= 4.6.0, < 5.11.6, fixed in 5.11.6; NuGet.CommandLine (NuGet) >= 6.0.0, < 6.0.6, fixed in 6.0.6; NuGet.Packaging (NuGet) >= 6.0.0, < 6.0.6, fixed in 6.0.6. Check your lockfile, including transitive dependencies.

What it is

NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability

From the GitHub advisory

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…

Weakness type: CWE-20.

Product: NuGet.CommandLine (NuGet) · Assigned by: microsoft · Published: 2024-01-09

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 2.78% probability of exploitation activity in the next 30 days; percentile 86.

Timeline

• 2024-01-09 — CVE record published by microsoft
• 2024-02-13 — GitHub-reviewed advisory GHSA-68w7-72jg-6qpp published (critical)
• 2025-06-03 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability msrc.microsoft.com

Vulnerability records

1. GitHub Advisory GHSA-68w7-72jg-6qpp github.com
2. CVE.org record CVE-2024-0057 cve.org
3. NVD entry CVE-2024-0057 nvd.nist.gov

Other references from the CVE record and advisory

1. security.netapp.com security.netapp.com
2. github.com github.com
3. github.com github.com
4. github.com github.com

Critical NuGet advisories · Today’s Security Digest