# GHSA-cgpw-2gph-2r9g: Microsoft is aware of a denial of service vulnerability in ASP.NET Core when a malformed request is terminated.

> An attacker can cause a denial of service in ASP.NET Core by sending a malformed request, requiring a patch to fix request handling.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2018

## What is GHSA-cgpw-2gph-2r9g?

GHSA-cgpw-2gph-2r9g is a denial of service vulnerability in Microsoft.AspNetCore.All, published on 16 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-cgpw-2gph-2r9g?

10 open source packages ship an affected version, including Microsoft.AspNetCore.All, Microsoft.AspNetCore.App and Microsoft.AspNetCore.Server.Kestrel.Core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.AspNetCore.All` | NuGet | From 2.0.0 | 2.0.9 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.0.0 | 2.0.9 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.1.0 | 2.1.2 |
| `Microsoft.AspNetCore.All` | NuGet | From 2.1.0 | 2.1.2 |
| `Microsoft.AspNetCore.App` | NuGet | From 2.1.0 | 2.1.2 |
| `Microsoft.AspNetCore.App` | NuGet | From 2.1.0 | 2.1.2 |
| `Microsoft.AspNetCore.Server.Kestrel.Core` | NuGet | From 2.0.0 | 2.0.4 |
| `Microsoft.AspNetCore.Server.Kestrel.Core` | NuGet | From 2.0.0 | 2.0.4 |
| `Microsoft.AspNetCore.Server.Kestrel.Core` | NuGet | From 2.1.0 | 2.1.2 |
| `Microsoft.AspNetCore.Server.Kestrel.Core` | NuGet | From 2.1.0 | 2.1.2 |

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

Upgrade Microsoft.AspNetCore.All to a fixed version for your release line: 2.0.9 or 2.1.2.

## Is GHSA-cgpw-2gph-2r9g being exploited?

There is no known exploitation of GHSA-cgpw-2gph-2r9g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cgpw-2gph-2r9g and fix it if it is affected.

What it is: GHSA-cgpw-2gph-2r9g is a denial of service vulnerability in Microsoft.AspNetCore.All, published on 16 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-cgpw-2gph-2r9g in the wild and no public exploit code.

Affected packages and fixed versions:
- Microsoft.AspNetCore.All (NuGet): affected from 2.0.0; fixed in 2.0.9
- Microsoft.AspNetCore.All (NuGet): affected from 2.0.0; fixed in 2.0.9
- Microsoft.AspNetCore.All (NuGet): affected from 2.1.0; fixed in 2.1.2
- Microsoft.AspNetCore.All (NuGet): affected from 2.1.0; fixed in 2.1.2
- Microsoft.AspNetCore.App (NuGet): affected from 2.1.0; fixed in 2.1.2
- Microsoft.AspNetCore.App (NuGet): affected from 2.1.0; fixed in 2.1.2
- Microsoft.AspNetCore.Server.Kestrel.Core (NuGet): affected from 2.0.0; fixed in 2.0.4
- Microsoft.AspNetCore.Server.Kestrel.Core (NuGet): affected from 2.0.0; fixed in 2.0.4
- Microsoft.AspNetCore.Server.Kestrel.Core (NuGet): affected from 2.1.0; fixed in 2.1.2
- Microsoft.AspNetCore.Server.Kestrel.Core (NuGet): affected from 2.1.0; fixed in 2.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-cgpw-2gph-2r9g/ (Markdown: https://insights.sbomify.com/GHSA-cgpw-2gph-2r9g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cgpw-2gph-2r9g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cgpw-2gph-2r9g/
Summaries are generated and may contain mistakes; the official description above is the record.