Improper Certificate Validation
Published 12 Apr 2022 · Updated 8 Nov 2023
Is your project on an affected System.Security.Cryptography.X509Certificates?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=4.0.0 <4.1.2
- Fixed in
- 4.1.2
dotnet add package System.Security.Cryptography.X509Certificates --version 4.1.2- Affected
- >=1.0.0 <2.0.3
- Fixed in
- 2.0.3
dotnet add package Microsoft.NETCore.App --version 2.0.3Details
.NET Core 1.0, 1.1, and 2.0 allow an unauthenticated attacker to remotely cause a denial of service attack against a .NET Core web application by improperly parsing certificate data. A denial of service vulnerability exists when .NET Core improperly handles parsing certificate data, aka ".NET CORE Denial Of Service Vulnerability".
Is GHSA-7mfr-774f-w5r9 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected System.Security.Cryptography.X509Certificates, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.