Is Microsoft.AspNetCore.All 2.1 vulnerable?
NuGet · 33 releases from 2.1.0 to 2.1.34 · latest Microsoft.AspNetCore.All is 2.2.8 · checked 18 Nov 2026
No known advisories in the last release
Microsoft.AspNetCore.All 2.1.34, the last 2.1 release, has no known advisories. 8 advisories affect earlier 2.1.x releases, so update to 2.1.34.
dotnet add package Microsoft.AspNetCore.All --version 2.1.34Is your project on an affected Microsoft.AspNetCore.All?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.1.x, affecting earlier releases
ASP.NET Core Denial of Service Vulnerability
- Affected
- >=2.1.0 <2.1.21
- Fixed in
- 2.1.21
Remote code execution in ASP.NET Core
- Affected
- >=2.1.0 <2.1.15
- Fixed in
- 2.1.15
Denial of service in ASP.NET Core
- Affected
- >=2.1.0 <2.1.15
- Fixed in
- 2.1.15
Open redirect in ASP.NET Core
- Affected
- >=2.2.0 <2.2.6 · >=2.1.0 <2.1.12
- Fixed in
- 2.1.12, 2.2.6
Denial of service in ASP.NET Core
- Affected
- >=2.2.0 <2.2.1 · >=2.1.0 <2.1.7
- Fixed in
- 2.1.7, 2.2.1
Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.App, and Microsoft.AspNetCore.Server.Kestrel.Core
- Affected
- >=2.0.0 <2.0.9 · >=2.1.0 <2.1.2
- Fixed in
- 2.0.9, 2.1.2
Denial of service in ASP.NET Core
- Affected
- >=2.1.0 <2.1.13 · >=2.2.0 <2.2.7
- Fixed in
- 2.1.13, 2.2.7
Denial of service vulnerability exists when System.IO.Pipelines improperly handles requests
- Affected
- >=2.1.0 <2.1.4
- Fixed in
- 2.1.4
Every Microsoft.AspNetCore.All 2.1.x release
Affected: 2.1.0 to 2.1.20. 2.1.21 and later are not affected. Latest Microsoft.AspNetCore.All: 2.2.8.
| Version | Known advisories |
|---|---|
| Microsoft.AspNetCore.All 2.1.34 | None |
| Microsoft.AspNetCore.All 2.1.31 | None |
| Microsoft.AspNetCore.All 2.1.30 | None |
| Microsoft.AspNetCore.All 2.1.29 | None |
| Microsoft.AspNetCore.All 2.1.28 | None |
| Microsoft.AspNetCore.All 2.1.27 | None |
| Microsoft.AspNetCore.All 2.1.26 | None |
| Microsoft.AspNetCore.All 2.1.25 | None |
| Microsoft.AspNetCore.All 2.1.24 | None |
| Microsoft.AspNetCore.All 2.1.23 | None |
| Microsoft.AspNetCore.All 2.1.22 | None |
| Microsoft.AspNetCore.All 2.1.21 | None |
| Microsoft.AspNetCore.All 2.1.20 | CVE-2020-1597 |
| Microsoft.AspNetCore.All 2.1.19 | CVE-2020-1597 |
| Microsoft.AspNetCore.All 2.1.18 | CVE-2020-1597 |
| Microsoft.AspNetCore.All 2.1.17 | CVE-2020-1597 |
| Microsoft.AspNetCore.All 2.1.16 | CVE-2020-1597 |
| Microsoft.AspNetCore.All 2.1.15 | CVE-2020-1597 |
| Microsoft.AspNetCore.All 2.1.14 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602 |
| Microsoft.AspNetCore.All 2.1.13 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602 |
| Microsoft.AspNetCore.All 2.1.12 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.11 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.10 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.9 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.8 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.7 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.6 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.5 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.4 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, CVE-2018-8269 |
| Microsoft.AspNetCore.All 2.1.3 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, CVE-2018-8269, CVE-2018-8409 |
| Microsoft.AspNetCore.All 2.1.2 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, CVE-2018-8269, CVE-2018-8409 |
| Microsoft.AspNetCore.All 2.1.1 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, GHSA-cgpw-2gph-2r9g, CVE-2018-8269, CVE-2018-8409 |
| Microsoft.AspNetCore.All 2.1.0 | CVE-2020-1597, CVE-2020-0603, CVE-2020-0602, CVE-2019-1075, CVE-2019-0564, GHSA-cgpw-2gph-2r9g, CVE-2018-8269, CVE-2018-8409 |
Which of your client projects are still on Microsoft.AspNetCore.All 2.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact Microsoft.AspNetCore.All version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other Microsoft.AspNetCore.All versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.