GHSA-j378-6mmw-hqfr
HIGHGHSA-j378-6mmw-hqfr is a high-severity (CVSS 7.5) vulnerability in Microsoft.AspNetCore.All. O3 Security confirms whether GHSA-j378-6mmw-hqfr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Denial of service vulnerability exists when System.IO.Pipelines improperly handles requests
Blast Radius
Microsoft.AspNetCore.All.NETMicrosoft.AspNetCore.App.NETSystem.IO.PipelinesReal-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
A denial of service vulnerability exists when System.IO.Pipelines improperly handles requests, aka "System.IO.Pipelines Denial of Service." This affects .NET Core 2.1, System.IO.Pipelines, ASP.NET Core 2.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Microsoft.AspNetCore.All | ≥ 2.1.0&&< 2.1.4 | 2.1.4 |
| .NETNuGet | Microsoft.AspNetCore.App | ≥ 2.1.0&&< 2.1.4 | 2.1.4 |
| .NETNuGet | System.IO.Pipelines | ≥ 4.5.0&&< 4.5.1 | 4.5.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.All. 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.AspNetCore.All to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j378-6mmw-hqfr 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-j378-6mmw-hqfr 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-j378-6mmw-hqfr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-j378-6mmw-hqfr in your dependencies?
O3 detects GHSA-j378-6mmw-hqfr across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.