HighGHSA-j378-6mmw-hqfrCVE-2018-8409

Denial of service vulnerability exists when System.IO.Pipelines improperly handles requests

Published 16 Oct 2018 · Updated 8 Dec 2024

Is your project on an affected Microsoft.AspNetCore.All?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.1.0 <2.1.4
Fixed in
2.1.4
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.All --version 2.1.4
Affected
>=2.1.0 <2.1.4
Fixed in
2.1.4
Update to the fixed version for your release line, for example:dotnet add package Microsoft.AspNetCore.App --version 2.1.4
Affected
>=4.5.0 <4.5.1
Fixed in
4.5.1
Update to the fixed version for your release line, for example:dotnet add package System.IO.Pipelines --version 4.5.1

Details

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.

Is GHSA-j378-6mmw-hqfr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Microsoft.AspNetCore.All, and gives you the command that fixes it.

More advisories for Microsoft.AspNetCore.All

  • HighCVE-2020-1597ASP.NET Core Denial of Service Vulnerability · 24 May 2022
  • HighCVE-2020-0603Remote code execution in ASP.NET Core · 24 May 2022
  • MediumCVE-2020-0602Denial of service in ASP.NET Core · 24 May 2022
  • MediumCVE-2019-1075Open redirect in ASP.NET Core · 24 May 2022
  • HighCVE-2017-11879Open redirect in ASP.NET Core · 14 May 2022
  • HighCVE-2019-0564Denial of service in ASP.NET Core · 14 May 2022
All 10 advisories for Microsoft.AspNetCore.All

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.