GHSA-xcvr-qv8h-m7xw — Microsoft.NETCore.Jit
HIGHGHSA-xcvr-qv8h-m7xw is a high-severity (CVSS 7.5) vulnerability in Microsoft.NETCore.Jit. A fix is available for Microsoft.NETCore.Jit — see the affected versions and patch details below.
.NET Core Denial of Service Vulnerability
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
GHSA-xcvr-qv8h-m7xw 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 379,842 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
Microsoft.NETCore.Jit.NETMicrosoft.NETCore.Jit.NETMicrosoft.NETCore.JitReal-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
.NET Core 1.0, .NET Core 1.1, NET Core 2.0 and PowerShell Core 6.0.0 allow a denial of Service vulnerability due to how specially crafted requests are handled, aka ".NET Core Denial of Service Vulnerability".
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Microsoft.NETCore.Jit | ≥ 2.0.0&&< 2.0.6 | 2.0.6dotnet add package Microsoft.NETCore.Jit --version 2.0.6 |
| .NETNuGet | Microsoft.NETCore.Jit | ≥ 1.1.0&&< 1.1.7 | 1.1.7dotnet add package Microsoft.NETCore.Jit --version 1.1.7 |
| .NETNuGet | Microsoft.NETCore.Jit | all versions | 1.0.12dotnet add package Microsoft.NETCore.Jit --version 1.0.12 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.Jit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.NETCore.Jit to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xcvr-qv8h-m7xw is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xcvr-qv8h-m7xw can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xcvr-qv8h-m7xw. 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-dotnet20-dotnet-0:2.0.6-1.el7 | RHSA-2018:0522 |
Frequently Asked Questions
Is GHSA-xcvr-qv8h-m7xw in your dependencies?
O3 Security finds GHSA-xcvr-qv8h-m7xw across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.