Denial of service in ASP.NET Core
CVE-2020-0602GHSA-23cv-jh4v-vffm
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (microsoft.aspnetcore.app.runtime.linux-arm64 3.1.1; microsoft.aspnetcore.all 2.1.15; microsoft.aspnetcore.app.runtime.osx-x64 3.1.1; microsoft.aspnetcore.app.runtime.linux-arm 3.1.1; microsoft.aspnetcore.app.runtime.win-x86 3.1.1; 6 more packages under Affected packages), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
NuGet microsoft.aspnetcore.app.runtime.linux-arm64
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.all
- Affected
- >= 2.1.0, < 2.1.15
- Fixed in
- 2.1.15
NuGet microsoft.aspnetcore.app.runtime.osx-x64
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.app.runtime.linux-arm
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.app.runtime.win-x86
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.app.runtime.linux-x64
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.app.runtime.win-arm
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.app.runtime.linux-musl-x64
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.app.runtime.win-x64
- Affected
- >= 3.1.0, < 3.1.1
- Fixed in
- 3.1.1
NuGet microsoft.aspnetcore.http.connections
- Affected
- >= 1.0.0, < 1.0.15
- Fixed in
- 1.0.15
NuGet microsoft.aspnetcore.app
- Affected
- >= 3.1.0, <= 3.1.0>= 3.0.0, <= 3.0.0>= 2.1.0, < 2.1.15
- Fixed in
- 3.1.1, 3.0.1, 2.1.15
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-23cv-jh4v-vffm lists affected ranges: NuGet microsoft.aspnetcore.all >=2.1.0 =3.1.0 =3.0.0 =2.1.0 =1.0.0 =3.1.0 =3.1.0 =3.1.0 <3.1.1; NuGet…
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- CVE-2020-0602: 7.61% estimated exploitation activity in the next 30 days; percentile 94.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka 'ASP.NET Core Denial of Service Vulnerability'.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-23cv-jh4v-vffm
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2020-0602 Advisory: Denial of service in ASP.NET Core IDs: CVE-2020-0602, GHSA-23cv-jh4v-vffm Record: https://patchnext.com/advisories/cve-2020-0602 (revision 1, source checked 26 Oct 2026, 16:58 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: microsoft.aspnetcore.app.runtime.linux-arm64 3.1.1; microsoft.aspnetcore.all 2.1.15; microsoft.aspnetcore.app.runtime.osx-x64 3.1.1; microsoft.aspnetcore.app.runtime.linux-arm 3.1.1; microsoft.aspnetcore.app.runtime.win-x86 3.1.1; microsoft.aspnetcore.app.runtime.linux-x64 3.1.1; microsoft.aspnetcore.app.runtime.win-arm 3.1.1; microsoft.aspnetcore.app.runtime.linux-musl-x64 3.1.1; microsoft.aspnetcore.app.runtime.win-x64 3.1.1; microsoft.aspnetcore.http.connections 1.0.15; microsoft.aspnetcore.app 3.1.1, 3.0.1, 2.1.15. A vendor fix does not mean a deployment is fixed. ## Affected components - NuGet microsoft.aspnetcore.app.runtime.linux-arm64: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.all: affected >= 2.1.0, < 2.1.15; fixed in 2.1.15 - NuGet microsoft.aspnetcore.app.runtime.osx-x64: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.app.runtime.linux-arm: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.app.runtime.win-x86: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.app.runtime.linux-x64: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.app.runtime.win-arm: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.app.runtime.linux-musl-x64: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.app.runtime.win-x64: affected >= 3.1.0, < 3.1.1; fixed in 3.1.1 - NuGet microsoft.aspnetcore.http.connections: affected >= 1.0.0, < 1.0.15; fixed in 1.0.15 - NuGet microsoft.aspnetcore.app: affected >= 3.1.0, <= 3.1.0; >= 3.0.0, <= 3.0.0; >= 2.1.0, < 2.1.15; fixed in 3.1.1, 3.0.1, 2.1.15 ## Suggested inspection (read-only) - NuGet microsoft.aspnetcore.app.runtime.linux-arm64: check the installed version with your package manager. - NuGet microsoft.aspnetcore.all: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.osx-x64: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.linux-arm: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.win-x86: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.linux-x64: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.win-arm: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.linux-musl-x64: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app.runtime.win-x64: check the installed version with your package manager. - NuGet microsoft.aspnetcore.http.connections: check the installed version with your package manager. - NuGet microsoft.aspnetcore.app: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on microsoft.aspnetcore.app.runtime.linux-arm64, microsoft.aspnetcore.all, microsoft.aspnetcore.app.runtime.osx-x64, microsoft.aspnetcore.app.runtime.linux-arm, microsoft.aspnetcore.app.runtime.win-x86, microsoft.aspnetcore.app.runtime.linux-x64, microsoft.aspnetcore.app.runtime.win-arm, microsoft.aspnetcore.app.runtime.linux-musl-x64, microsoft.aspnetcore.app.runtime.win-x64, microsoft.aspnetcore.http.connections, microsoft.aspnetcore.app. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-23cv-jh4v-vffm (GitHub-reviewed advisory GHSA-23cv-jh4v-vffm lists affected ranges: NuGet microsoft.aspnetcore.all >=2.1.0 =3.1.0 =3.0.0 =2.1.0 =1.0.0 =3.1.0 =3.1.0 =3.1.0 <3.1.1; NuGet…) Commands are suggestions: review each one before running it.
Loading voting…