BouncyCastle.Cryptography vulnerabilities

BouncyCastle.NET is a popular cryptography library for .NET

Registry
NuGet
Latest
2.7.0
License
MIT

3 known advisories

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

Update to the latest version:dotnet add package BouncyCastle.Cryptography --version 2.7.0

Is your project on an affected BouncyCastle.Cryptography?

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 BouncyCastle.Cryptography

  • MediumCVE-2024-29857GHSA-8xfc-gm6g-vgpv14 May 2024

    Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.

    Affected
    <2.3.1
    Fixed in
    2.3.1
  • MediumCVE-2024-30172GHSA-m44j-cfrm-g8qc14 May 2024

    Bouncy Castle crafted signature and public key can be used to trigger an infinite loop

    Affected
    <2.3.1
    Fixed in
    2.3.1
  • MediumCVE-2024-30171GHSA-v435-xc8x-wvr914 May 2024

    Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")

    Affected
    <2.3.1
    Fixed in
    2.3.1

Is your BouncyCastle.Cryptography version vulnerable?

Which of your client projects still run an old BouncyCastle.Cryptography?

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.