Is BouncyCastle.Cryptography 2.2 vulnerable?
NuGet · 2 releases from 2.2.0 to 2.2.1 · latest BouncyCastle.Cryptography is 2.7.0 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. BouncyCastle.Cryptography 2.2.1, the last 2.2 release, is affected by 3 known security advisories (3 medium), including CVE-2024-29857, CVE-2024-30172, CVE-2024-30171. Upgrade to 2.3.1 or later to fix all of them.
dotnet add package BouncyCastle.Cryptography --version 2.3.1Is your project on an affected BouncyCastle.Cryptography?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting BouncyCastle.Cryptography 2.2.1
Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
- Affected
- <2.3.1
- Fixed in
- 2.3.1
Bouncy Castle crafted signature and public key can be used to trigger an infinite loop
- Affected
- <2.3.1
- Fixed in
- 2.3.1
Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")
- Affected
- <2.3.1
- Fixed in
- 2.3.1
Every BouncyCastle.Cryptography 2.2.x release
Affected: 2.2.0 to 2.2.1. Latest BouncyCastle.Cryptography: 2.7.0.
| Version | Known advisories |
|---|---|
| BouncyCastle.Cryptography 2.2.1 | CVE-2024-29857, CVE-2024-30172, CVE-2024-30171 |
| BouncyCastle.Cryptography 2.2.0 | CVE-2024-29857, CVE-2024-30172, CVE-2024-30171 |
Which of your client projects are still on BouncyCastle.Cryptography 2.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact BouncyCastle.Cryptography version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other BouncyCastle.Cryptography 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.