System.Security.Cryptography.X509Certificates vulnerabilities

Provides types for reading, exporting and verifying Authenticode X.509 v3 certificates. These certificates are signed with a private key that uniquely and positively identifies the holder of the certificate. Commonly Used Types: System.Security.Cryptography.X509Certificates.X509Certificate2 System.Security.Cryptography.X509Certificates.X509Certificate System.Security.Cryptography.X509Certificates.X509ContentType System.Security.Cryptography.X509Certificates.StoreLocation System.Security.Cryptography.X509Certificates.StoreName System.Security.Cryptography.X509Certificates.X509FindType System.Security.Cryptography.X509Certificates.X509ChainStatus System.Security.Cryptography.X509Certificates.X509Certificate2Collection System.Security.Cryptography.X509Certificates.X509EnhancedKeyUsageExtension System.Security.Cryptography.X509Certificates.X509Chain When using NuGet 3.x this package requires at least version 3.4.

Registry
NuGet
Latest
4.3.2

1 known advisory

The latest version, 4.3.2, is not affected by any of them. Projects on older versions may be.

Update to the latest version:dotnet add package System.Security.Cryptography.X509Certificates --version 4.3.2

Is your project on an affected System.Security.Cryptography.X509Certificates?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for System.Security.Cryptography.X509Certificates

  • HighCVE-2017-11770GHSA-7mfr-774f-w5r912 Apr 2022

    Improper Certificate Validation

    Affected
    >=4.0.0 <4.1.2
    Fixed in
    4.1.2

Is your System.Security.Cryptography.X509Certificates version vulnerable?

Which of your client projects still run an old System.Security.Cryptography.X509Certificates?

NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other NuGet packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.