Skip to content

NuGet Client Security Feature Bypass Vulnerability

Critical severity GitHub Reviewed Published Feb 13, 2024 in NuGet/NuGet.Client • Updated Apr 16, 2024

Package

nuget NuGet.CommandLine (NuGet)

Affected versions

>= 4.6.0, < 5.11.6
>= 6.0.0, < 6.0.6
>= 6.3.0, < 6.3.4
>= 6.4.0, < 6.4.3
>= 6.6.0, < 6.6.2
= 6.7.0
= 6.8.0

Patched versions

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

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.

Other details

Announcement for this issue can be found at NuGet/Announcements#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

References

@martinrrm martinrrm published to NuGet/NuGet.Client Feb 13, 2024
Published to the GitHub Advisory Database Feb 13, 2024
Reviewed Feb 13, 2024
Last updated Apr 16, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.119%
(48th percentile)

Weaknesses

No CWEs

CVE ID

CVE-2024-0057

GHSA ID

GHSA-68w7-72jg-6qpp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.