How severe is GHSA-xcvr-qv8h-m7xw?

GHSA-xcvr-qv8h-m7xw has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xcvr-qv8h-m7xw?

GHSA-xcvr-qv8h-m7xw affects the following packages: Microsoft.NETCore.Jit (NuGet), Microsoft.NETCore.Jit (NuGet), Microsoft.NETCore.Jit (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-xcvr-qv8h-m7xw?

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.

How do I detect GHSA-xcvr-qv8h-m7xw in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.Jit. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xcvr-qv8h-m7xw if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-xcvr-qv8h-m7xw?

O3 pinpoints whether GHSA-xcvr-qv8h-m7xw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xcvr-qv8h-m7xw actively exploited in the wild?

No public exploit code has been indexed for GHSA-xcvr-qv8h-m7xw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xcvr-qv8h-m7xw published, and has it been updated?

GHSA-xcvr-qv8h-m7xw was published on May 13, 2022 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-xcvr-qv8h-m7xw

HIGH

GHSA-xcvr-qv8h-m7xw is a high-severity (CVSS 7.5) vulnerability in Microsoft.NETCore.Jit. O3 Security confirms whether GHSA-xcvr-qv8h-m7xw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

.NET Core Denial of Service Vulnerability

Also known asCVE-2018-0875

Published

May 13, 2022

Updated

Nov 28, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

.NETMicrosoft.NETCore.Jit.NETMicrosoft.NETCore.Jit.NETMicrosoft.NETCore.Jit

Real-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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.NETCore.Jit`	≥ 2.0.0&&< 2.0.6	2.0.6
.NETNuGet	`Microsoft.NETCore.Jit`	≥ 1.1.0&&< 1.1.7	1.1.7
.NETNuGet	`Microsoft.NETCore.Jit`	all versions	1.0.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NETCore.Jit. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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 pinpoints whether GHSA-xcvr-qv8h-m7xw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-xcvr-qv8h-m7xw in your dependencies?

O3 detects GHSA-xcvr-qv8h-m7xw across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works