CVE-2018-8409: Denial of service vulnerability exists when System.IO.Pipelines improperly handles requests

Quick answers

Is CVE-2018-8409 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2018-8409 being exploited in the wild.

How severe is CVE-2018-8409?

Low severity, with a CVSS score of 3.1, published 16 October 2018.

Which products and versions are affected?

Microsoft.AspNetCore.All (NuGet) ECOSYSTEM:introduced=2.1.0,fixed=2.1.4; Microsoft.AspNetCore.App (NuGet) ECOSYSTEM:introduced=2.1.0,fixed=2.1.4; System.IO.Pipelines (NuGet) ECOSYSTEM:introduced=4.5.0,fixed=4.5.1.

Is there a fix for CVE-2018-8409?

Yes. Microsoft.AspNetCore.All (NuGet): upgrade to 2.1.4 or later; Microsoft.AspNetCore.App (NuGet): upgrade to 2.1.4 or later; System.IO.Pipelines (NuGet): upgrade to 4.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2018-8409?

Check whether you run Microsoft.AspNetCore.All (NuGet), Microsoft.AspNetCore.App (NuGet) or System.IO.Pipelines (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• Microsoft.AspNetCore.All (NuGet): upgrade to 2.1.4 or later

  dotnet add package Microsoft.AspNetCore.All --version 2.1.4

• Microsoft.AspNetCore.App (NuGet): upgrade to 2.1.4 or later

  dotnet add package Microsoft.AspNetCore.App --version 2.1.4

• System.IO.Pipelines (NuGet): upgrade to 4.5.1 or later

  dotnet add package System.IO.Pipelines --version 4.5.1

Affected products

• Microsoft.AspNetCore.All (NuGet) ECOSYSTEM:introduced=2.1.0,fixed=2.1.4
• Microsoft.AspNetCore.App (NuGet) ECOSYSTEM:introduced=2.1.0,fixed=2.1.4
• System.IO.Pipelines (NuGet) ECOSYSTEM:introduced=4.5.0,fixed=4.5.1

Identifiers

• CVE-2018-8409
• GHSA-j378-6mmw-hqfr