Local code execution via permissive NuGet paths
Published Oct 11, 2022 · Updated Feb 28, 2025
Improper privilege management in NuGet clients bundled with affected .NET and Visual Studio releases allows local users to execute code. NuGet's shared-directory helper creates cache, lock, and configuration paths with permissions broader than the user's effective umask on POSIX systems. A local user with access to those paths can replace files later consumed by a more privileged NuGet process and execute code in that process's context.
Summary
What happened
Improper privilege management in NuGet clients bundled with affected .NET and Visual Studio releases allows local users to execute code. NuGet's shared-directory helper creates cache, lock, and configuration paths with permissions broader than the user's effective umask on POSIX systems. A local user with access to those paths can replace files later consumed by a more privileged NuGet process and execute code in that process's context.
The record
- CVE
- CVE-2022-41032
- Published
- Oct 11, 2022
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-269
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- Feb 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.0.0 <16.9.26
- Affected versionversion=16.11.0 <16.11.20
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo