# CVE-2022-41032: NuGet Client Elevation of Privilege Vulnerability > An attacker can exploit the NuGet Client to elevate privileges on systems using affected .NET and Visual Studio versions. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 11 Oct 2022 - **Updated:** 28 Feb 2025 - **Also known as:** ALSA-2022:6911, ALSA-2022:6912, ALSA-2022:6913, ALSA-2022:7826, ALSA-2022:8434, BIT-dotnet-2022-41032, BIT-dotnet-sdk-2022-41032, CLEANSTART-2024-PD73825, GHSA-g3q9-xf95-8hp5, RHSA-2022:6911, RHSA-2022:6912, RHSA-2022:6913, RHSA-2022:6914, RHSA-2022:6915, RHSA-2022:7826, RHSA-2022:8434, RLSA-2022:6911, RLSA-2022:6912, RLSA-2022:6913, UBUNTU-CVE-2022-41032, USN-5670-1 ## What is CVE-2022-41032? CVE-2022-41032 is a high-severity vulnerability in Fedoraproject Fedora, published on 11 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description NuGet Client Elevation of Privilege Vulnerability Weakness: CWE-269 (Improper Privilege Management) ## Which versions are affected by CVE-2022-41032? 40 open source packages ship an affected version, including NuGet.CommandLine, dotnet and dotnet-sdk. It affects 5 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `NuGet.CommandLine` | NuGet | From 4.6.0 | 4.9.6 | | `NuGet.CommandLine` | NuGet | From 4.6.0 | 4.9.6 | | `NuGet.CommandLine` | NuGet | From 5.0.0 | 5.7.3 | | `NuGet.CommandLine` | NuGet | From 5.0.0 | 5.7.3 | | `NuGet.CommandLine` | NuGet | From 5.10.0 | 5.11.3 | | `NuGet.CommandLine` | NuGet | From 5.10.0 | 5.11.3 | | `NuGet.CommandLine` | NuGet | From 5.8.0 | 5.9.3 | | `NuGet.CommandLine` | NuGet | From 5.8.0 | 5.9.3 | | `NuGet.CommandLine` | NuGet | From 6.0.0 | 6.0.3 | | `NuGet.CommandLine` | NuGet | From 6.0.0 | 6.0.3 | | `NuGet.CommandLine` | NuGet | From 6.1.0 | 6.2.2 | | `NuGet.CommandLine` | NuGet | From 6.1.0 | 6.2.2 | | `NuGet.CommandLine` | NuGet | From 6.3.0 | 6.3.1 | | `NuGet.CommandLine` | NuGet | From 6.3.0 | 6.3.1 | | `dotnet` | Bitnami | From 6.0.0 | 6.0.1 | | `dotnet-sdk` | Bitnami | From 6.0.0 | 6.0.1 | | `NuGet.Commands` | NuGet | From 4.6.0 | 4.9.6 | | `NuGet.Commands` | NuGet | From 4.6.0 | 4.9.6 | | `NuGet.Commands` | NuGet | From 5.0.0 | 5.7.3 | | `NuGet.Commands` | NuGet | From 5.0.0 | 5.7.3 | | `NuGet.Commands` | NuGet | From 5.10.0 | 5.11.3 | | `NuGet.Commands` | NuGet | From 5.10.0 | 5.11.3 | | `NuGet.Commands` | NuGet | From 5.8.0 | 5.9.3 | | `NuGet.Commands` | NuGet | From 5.8.0 | 5.9.3 | | `NuGet.Commands` | NuGet | From 6.0.0 | 6.0.3 | | `NuGet.Commands` | NuGet | From 6.0.0 | 6.0.3 | | `NuGet.Commands` | NuGet | From 6.1.0 | 6.2.2 | | `NuGet.Commands` | NuGet | From 6.1.0 | 6.2.2 | | `NuGet.Commands` | NuGet | From 6.3.0 | 6.3.1 | | `NuGet.Commands` | NuGet | From 6.3.0 | 6.3.1 | | `NuGet.Protocol` | NuGet | From 4.6.0 | 4.9.6 | | `NuGet.Protocol` | NuGet | From 4.6.0 | 4.9.6 | | `NuGet.Protocol` | NuGet | From 5.0.0 | 5.7.3 | | `NuGet.Protocol` | NuGet | From 5.0.0 | 5.7.3 | | `NuGet.Protocol` | NuGet | From 5.10.0 | 5.11.3 | | `NuGet.Protocol` | NuGet | From 5.10.0 | 5.11.3 | | `NuGet.Protocol` | NuGet | From 5.8.0 | 5.9.3 | | `NuGet.Protocol` | NuGet | From 5.8.0 | 5.9.3 | | `NuGet.Protocol` | NuGet | From 6.0.0 | 6.0.3 | | `NuGet.Protocol` | NuGet | From 6.0.0 | 6.0.3 | Products: Fedoraproject Fedora, Microsoft .Net, Microsoft .Net Core, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022. ## How do I fix CVE-2022-41032? Upgrade NuGet.CommandLine to a fixed version for your release line: 4.9.6, 5.7.3, 5.11.3 or 5.9.3. ## Is CVE-2022-41032 being exploited? There is no known exploitation of CVE-2022-41032 in the wild and no public exploit code. Public exploit code: - Reproduction / example repository for CVE 2022-41032. (github_poc): https://github.com/ethomson/cve-2022-41032 ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-41032 and fix it if it is affected. What it is: CVE-2022-41032 is a high-severity vulnerability in Fedoraproject Fedora, published on 11 Oct 2022. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-41032 in the wild and no public exploit code. Affected packages and fixed versions: - NuGet.CommandLine (NuGet): affected from 4.6.0; fixed in 4.9.6 - NuGet.CommandLine (NuGet): affected from 4.6.0; fixed in 4.9.6 - NuGet.CommandLine (NuGet): affected from 5.0.0; fixed in 5.7.3 - NuGet.CommandLine (NuGet): affected from 5.0.0; fixed in 5.7.3 - NuGet.CommandLine (NuGet): affected from 5.10.0; fixed in 5.11.3 - NuGet.CommandLine (NuGet): affected from 5.10.0; fixed in 5.11.3 - NuGet.CommandLine (NuGet): affected from 5.8.0; fixed in 5.9.3 - NuGet.CommandLine (NuGet): affected from 5.8.0; fixed in 5.9.3 - NuGet.CommandLine (NuGet): affected from 6.0.0; fixed in 6.0.3 - NuGet.CommandLine (NuGet): affected from 6.0.0; fixed in 6.0.3 - NuGet.CommandLine (NuGet): affected from 6.1.0; fixed in 6.2.2 - NuGet.CommandLine (NuGet): affected from 6.1.0; fixed in 6.2.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-41032/ (Markdown: https://insights.sbomify.com/CVE-2022-41032/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41032 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41032 - OSV: https://osv.dev/vulnerability/CVE-2022-41032 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-41032/ Summaries are generated and may contain mistakes; the official description above is the record.