How severe is GHSA-cgpw-2gph-2r9g?

No CVSS score has been assigned to GHSA-cgpw-2gph-2r9g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cgpw-2gph-2r9g?

GHSA-cgpw-2gph-2r9g affects the following packages: Microsoft.AspNetCore.Server.Kestrel.Core (NuGet), Microsoft.AspNetCore.All (NuGet), Microsoft.AspNetCore.App (NuGet), Microsoft.AspNetCore.Server.Kestrel.Core (NuGet), Microsoft.AspNetCore.All (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-cgpw-2gph-2r9g?

Update Microsoft.AspNetCore.Server.Kestrel.Core to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cgpw-2gph-2r9g is resolved across your whole dependency graph.

How do I detect GHSA-cgpw-2gph-2r9g in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Server.Kestrel.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cgpw-2gph-2r9g if there is no patch (or I can't update yet)?

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.

Is GHSA-cgpw-2gph-2r9g actively exploited in the wild?

No public exploit code has been indexed for GHSA-cgpw-2gph-2r9g 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-cgpw-2gph-2r9g published, and has it been updated?

GHSA-cgpw-2gph-2r9g was published on October 16, 2018 and was last updated on December 2, 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

Not in CISA KEV

Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.App, and Microsoft.AspNetCore.Server.Kestrel.CoreGHSA-cgpw-2gph-2r9g

GHSA-cgpw-2gph-2r9g is a security vulnerability in Microsoft.AspNetCore.Server.Kestrel.Core. A fix is available for Microsoft.AspNetCore.Server.Kestrel.Core — see the affected versions and patch details below.

Published

Oct 16, 2018

Updated

Dec 2, 2024

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected

.NETMicrosoft.AspNetCore.Server.Kestrel.Core.NETMicrosoft.AspNetCore.All.NETMicrosoft.AspNetCore.App.NETMicrosoft.AspNetCore.Server.Kestrel.Core.NETMicrosoft.AspNetCore.All

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

The update addresses the vulnerability by correcting how ASP.NET Core handles such requests.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.Server.Kestrel.Core`	≥ 2.0.0&&< 2.0.4	2.0.4`dotnet add package Microsoft.AspNetCore.Server.Kestrel.Core --version 2.0.4`
.NETNuGet	`Microsoft.AspNetCore.All`	≥ 2.0.0&&< 2.0.9	2.0.9`dotnet add package Microsoft.AspNetCore.All --version 2.0.9`
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 2.1.0&&< 2.1.2	2.1.2`dotnet add package Microsoft.AspNetCore.App --version 2.1.2`
.NETNuGet	`Microsoft.AspNetCore.Server.Kestrel.Core`	≥ 2.1.0&&< 2.1.2	2.1.2`dotnet add package Microsoft.AspNetCore.Server.Kestrel.Core --version 2.1.2`
.NETNuGet	`Microsoft.AspNetCore.All`	≥ 2.1.0&&< 2.1.2	2.1.2`dotnet add package Microsoft.AspNetCore.All --version 2.1.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Server.Kestrel.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.AspNetCore.Server.Kestrel.Core to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cgpw-2gph-2r9g 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.

Frequently Asked Questions

Microsoft is aware of a denial of service vulnerability in ASP.NET Core when a malformed request is terminated. An attacker who successfully exploited this vulnerability could cause a denial of service attack. The update addresses the vulnerability by correcting how ASP.NET Core handles such requests.

O3 Security · Impact-Aware SCA

Is GHSA-cgpw-2gph-2r9g in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works