CVE-2022-30184 is a medium-severity (CVSS 5.5) Information Exposure vulnerability in NuGet.Commands. A fix is available for NuGet.Commands — see the affected versions and patch details below.
Potential leak of NuGet.org API key
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-30184.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-30184 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
NuGet.Commands.NETNuGet.CommandLine.NETNuGet.CommandLine.XPlat.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands.NETNuGet.Commands+13 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Description
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 6.0 and .NET Core 3.1, NuGet (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat version range from 3.5.0 to 6.2.0). This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A vulnerability exists in .NET 6.0, .NET Core 3.1, and NuGet (NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat version range from 3.5.0 to 6.2.0) where a nuget.org api key could leak due to an incorrect comparison with a server url.
Affected software
NuGet & NuGet Packages
- Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat 6.2.0 version or earlier.
- Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat 6.0.1 version or earlier.
- Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat 5.11.1 version or earlier.
- Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat 5.9.1 version or earlier.
- Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat 5.7.1 version or earlier.
- Any NuGet.exe, NuGet.Commands, NuGet.CommandLine, NuGet.CommandLine.XPlat 4.9.4 version or earlier.
.NET SDK(s)
- Any .NET 6.0 application running on .NET 6.0.5 or earlier.
- Any .NET 3.1 application running on .NET Core 3.1.25 or earlier.
Patches
-
If you're using NuGet.exe 6.2.0 or lower, you should download and install 6.2.1 from https://dist.nuget.org/win-x86-commandline/v6.2.1/nuget.exe.
-
If you're using NuGet.exe 6.0.1 or lower, you should download and install 6.0.2 from https://dist.nuget.org/win-x86-commandline/v6.0.2/nuget.exe.
-
If you're using NuGet.exe 5.11.1 or lower, you should download and install 5.11.2 from https://dist.nuget.org/win-x86-commandline/v5.11.2/nuget.exe.
-
If you're using NuGet.exe 5.9.1 or lower, you should download and install 5.9.2 from https://dist.nuget.org/win-x86-commandline/v5.9.2/nuget.exe.
-
If you're using NuGet.exe 5.7.1 or lower, you should download and install 5.7.2 from https://dist.nuget.org/win-x86-commandline/v4.7.2/nuget.exe.
-
If you're using NuGet.exe 4.9.4 or lower, you should download and install 4.9.5 from https://dist.nuget.org/win-x86-commandline/v4.9.5/nuget.exe.
-
If you're using .NET Core 6.0, you should download and install Runtime 6.0.6 or SDK 6.0.106 (for Visual Studio 2022 v17.0) or SDK 6.0.301 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
-
If you're using .NET Core 3.1, you should download and install Runtime 3.1.26 or SDK 3.1.420 (for Visual Studio 2019 v16.9 or Visual Studio 2011 16.11 or Visual Studio 2022 17.0 or Visual Studio 2022 17.1 ) from https://dotnet.microsoft.com/download/dotnet-core/3.1
.NET 6.0 and .NET Core 3.1 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.
Other Details
Announcement for this issue can be found at https://github.com/NuGet/Announcements/issues/62
MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2022-30184
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | NuGet.Commands | ≥ 3.5.0&&< 4.9.5 | 4.9.5dotnet add package NuGet.Commands --version 4.9.5 |
| .NETNuGet | NuGet.CommandLine | ≥ 3.5.0&&< 4.9.5 | 4.9.5dotnet add package NuGet.CommandLine --version 4.9.5 |
| .NETNuGet | NuGet.CommandLine.XPlat | ≥ 3.5.0&&< 4.9.5 | 4.9.5dotnet add package NuGet.CommandLine.XPlat --version 4.9.5 |
| .NETNuGet | NuGet.Commands | ≥ 5.0.0&&< 5.2.1 | 5.2.1dotnet add package NuGet.Commands --version 5.2.1 |
| .NETNuGet | NuGet.Commands | ≥ 5.3.0&&< 5.7.2 | 5.7.2dotnet add package NuGet.Commands --version 5.7.2 |
| .NETNuGet | NuGet.Commands | ≥ 5.8.0&&< 5.9.2 | 5.9.2dotnet add package NuGet.Commands --version 5.9.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for NuGet.Commands, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update NuGet.Commands to 4.9.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30184 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-30184 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-30184. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| .NET Core on Red Hat Enterprise Linux | rh-dotnet31-dotnet-0:3.1.420-1.el7_9 | RHSA-2022:5062 |
| .NET Core on Red Hat Enterprise Linux | rh-dotnet60-dotnet-0:6.0.106-1.el7_9 | RHSA-2022:5047 |
| Red Hat Enterprise Linux 8 | dotnet6.0-0:6.0.106-1.el8_6 | RHSA-2022:5046 |
| Red Hat Enterprise Linux 8 | dotnet3.1-0:3.1.420-1.el8_6 | RHSA-2022:5061 |
| Red Hat Enterprise Linux 9 | dotnet6.0-0:6.0.106-1.el9_0 | RHSA-2022:5050 |
Frequently Asked Questions
Is CVE-2022-30184 in your dependencies?
O3 Security finds CVE-2022-30184 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.