What is CVE-2020-0602?

CVE-2020-0602 is a medium-severity uncontrolled resource consumption vulnerability in Microsoft.AspNetCore.All (nuget), affecting versions >= 2.1.0, < 2.1.15. It is fixed in 2.1.15, 3.1.1, 3.0.1, 1.0.15. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which packages are affected by CVE-2020-0602?

Microsoft.AspNetCore.All (nuget) versions >= 2.1.0, = 1.0.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, < 3.1.1.

Is there a fix for CVE-2020-0602?

Yes. CVE-2020-0602 is fixed in 2.1.15, 3.1.1, 3.0.1, 1.0.15. Upgrade to this version or later.

Is CVE-2020-0602 exploitable, and should I be worried?

Whether CVE-2020-0602 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-0602 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2020-0602 in Microsoft.AspNetCore.All

Q: Which packages are affected by CVE-2020-0602?

Microsoft.AspNetCore.All (nuget) versions >= 2.1.0, = 1.0.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, = 3.1.0, < 3.1.1.

Q: Is there a fix for CVE-2020-0602?

Yes. CVE-2020-0602 is fixed in 2.1.15, 3.1.1, 3.0.1, 1.0.15. Upgrade to this version or later.

Q: Is CVE-2020-0602 exploitable, and should I be worried?

Whether CVE-2020-0602 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-0602 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-0602?

Upgrade: Microsoft.AspNetCore.All to 2.1.15 or later, Microsoft.AspNetCore.App to 3.1.1 or later, Microsoft.AspNetCore.App to 3.0.1 or later, Microsoft.AspNetCore.App to 2.1.15 or later, Microsoft.AspNetCore.Http.Connections to 1.0.15 or later, Microsoft.AspNetCore.App.Runtime.linux-arm to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.linux-arm64 to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.linux-musl-x64 to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.linux-x64 to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.osx-x64 to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.win-arm to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.win-x64 to 3.1.1 or later, Microsoft.AspNetCore.App.Runtime.win-x86 to 3.1.1 or later.

Summary

Denial of service in ASP.NET Core

A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka 'ASP.NET Core Denial of Service Vulnerability'.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

Microsoft.AspNetCore.All (>= 2.1.0, < 2.1.15) Microsoft.AspNetCore.App (= 3.1.0) Microsoft.AspNetCore.App (= 3.0.0) Microsoft.AspNetCore.App (>= 2.1.0, < 2.1.15) Microsoft.AspNetCore.Http.Connections (>= 1.0.0, < 1.0.15) Microsoft.AspNetCore.App.Runtime.linux-arm (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.linux-arm64 (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.linux-musl-x64 (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.linux-x64 (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.osx-x64 (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.win-arm (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.win-x64 (>= 3.1.0, < 3.1.1) Microsoft.AspNetCore.App.Runtime.win-x86 (>= 3.1.0, < 3.1.1)

Security releases

Microsoft.AspNetCore.All → 2.1.15 (nuget) Microsoft.AspNetCore.App → 3.1.1 (nuget) Microsoft.AspNetCore.App → 3.0.1 (nuget) Microsoft.AspNetCore.App → 2.1.15 (nuget) Microsoft.AspNetCore.Http.Connections → 1.0.15 (nuget) Microsoft.AspNetCore.App.Runtime.linux-arm → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.linux-arm64 → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.linux-musl-x64 → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.linux-x64 → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.osx-x64 → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.win-arm → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.win-x64 → 3.1.1 (nuget) Microsoft.AspNetCore.App.Runtime.win-x86 → 3.1.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Microsoft.AspNetCore.All to 2.1.15 or later; Microsoft.AspNetCore.App to 3.1.1 or later; Microsoft.AspNetCore.App to 3.0.1 or later; Microsoft.AspNetCore.App to 2.1.15 or later; Microsoft.AspNetCore.Http.Connections to 1.0.15 or later; Microsoft.AspNetCore.App.Runtime.linux-arm to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.linux-arm64 to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.linux-musl-x64 to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.linux-x64 to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.osx-x64 to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.win-arm to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.win-x64 to 3.1.1 or later; Microsoft.AspNetCore.App.Runtime.win-x86 to 3.1.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-0602? CVE-2020-0602 is a medium-severity uncontrolled resource consumption vulnerability in Microsoft.AspNetCore.All (nuget), affecting versions >= 2.1.0, < 2.1.15. It is fixed in 2.1.15, 3.1.1, 3.0.1, 1.0.15. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which packages are affected by CVE-2020-0602?
- Microsoft.AspNetCore.All (nuget) (versions >= 2.1.0, < 2.1.15)
- Microsoft.AspNetCore.App (nuget) (versions = 3.1.0)
- Microsoft.AspNetCore.Http.Connections (nuget) (versions >= 1.0.0, < 1.0.15)
- Microsoft.AspNetCore.App.Runtime.linux-arm (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.linux-arm64 (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.linux-musl-x64 (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.linux-x64 (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.osx-x64 (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.win-arm (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.win-x64 (nuget) (versions >= 3.1.0, < 3.1.1)
- Microsoft.AspNetCore.App.Runtime.win-x86 (nuget) (versions >= 3.1.0, < 3.1.1)
Is there a fix for CVE-2020-0602? Yes. CVE-2020-0602 is fixed in 2.1.15, 3.1.1, 3.0.1, 1.0.15. Upgrade to this version or later.
Is CVE-2020-0602 exploitable, and should I be worried? Whether CVE-2020-0602 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-0602 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-0602?
- Upgrade Microsoft.AspNetCore.All to 2.1.15 or later
- Upgrade Microsoft.AspNetCore.App to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App to 3.0.1 or later
- Upgrade Microsoft.AspNetCore.App to 2.1.15 or later
- Upgrade Microsoft.AspNetCore.Http.Connections to 1.0.15 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.linux-arm to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.linux-arm64 to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.linux-musl-x64 to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.linux-x64 to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.osx-x64 to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.win-arm to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.win-x64 to 3.1.1 or later
- Upgrade Microsoft.AspNetCore.App.Runtime.win-x86 to 3.1.1 or later

Other vulnerabilities in Microsoft.AspNetCore.All

CVE-IDSeverityPackage summary

CVE-2020-1597HighMicrosoft.AspNetCore.App: ASP.NET Core Denial of Service Vulnerability CVE-2020-0603HighMicrosoft.AspNetCore.All: Remote code execution in ASP.NET Core CVE-2019-1075MediumMicrosoft.AspNetCore.App: Open redirect in ASP.NET Core CVE-2017-11879HighMicrosoft.AspNetCore.All: Open redirect in ASP.NET Core CVE-2019-0564HighMicrosoft.AspNetCore.WebSockets: Denial of service in ASP.NET Core