CVE-2023-29337: NuGet Client Remote Code Execution Vulnerability

Overview

Severity
High (CVSS 7.1)
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Category
Remote Code Execution
Exploit Status
Not Exploited
Exploitation Likelihood
Less Likely
Patch Tuesday
2023-Jun
Released
2023-06-13
Last Updated
2023-08-08
EPSS Score
0.34% (percentile: 56.7%)

FAQ

According to the CVSS metric, user interaction is required (UI:R) and privileges required is low (PR:L). What does that mean for this vulnerability? An authorized attacker must be on the machine and monitoring for actions as a step to exploit the race condition. According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? Successful exploitation of this vulnerability requires an attacker to win a race condition. How could an attacker exploit this vulnerability? A local attacker in the environment could exploit a race condition that allows a symlink attack when the victim user on the same system runs the nuget command. According to the CVSS metric, the attack vector is network (AV:N), and privilege required is low (PR:L). What is the target used in the context of the remote code execution? The attacker for this vulnerability could target the server accounts in an arbitrary or remote code execution. As an authenticated user, the attacker could attempt to trigger malicious code in the context of the server's account through a network call. The privilege requirement is low because the attacker needs to be authenticated as a normal user.

Affected Products (7)

Developer Tools

  • NuGet 6.2.3
  • NuGet 6.4.1
  • NuGet 6.5.0
  • NuGet 6.3.2
  • NuGet 6.0.4
  • NuGet 6.6.0
  • NuGet 5.11.4

Security Updates (1)

Acknowledgments

Kalle Niemitalo

Revision History

  • 2023-06-13: Information published.
  • 2023-08-08: The following revisions have been made in the Security Updates table: 1) Added Nuget 5.11.4 as it is affected by this vulnerability. See https://github.com/NuGet/Home/issues/12653 for more information. 2) Corrected the Build Numbers for all affected versions of Nuget.