Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
Published 14 May 2024 · Updated 10 Sept 2026
Is your project on an affected org.bouncycastle:bcprov-jdk18on?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk18on -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk15on -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk15to18 -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk14 -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bctls-jdk18on -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bctls-jdk14 -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.78
- Fixed in
- 1.78
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bctls-jdk15to18 -DdepVersion=1.78 -DforceVersion=true- Affected
- <1.0.2.5
- Fixed in
- 1.0.2.5
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bc-fips -DdepVersion=1.0.2.5 -DforceVersion=true- Affected
- All versions
- Fixed in
- No fix released
- Affected
- <2.3.1
- Fixed in
- 2.3.1
dotnet add package BouncyCastle.Cryptography --version 2.3.1Details
An issue was discovered in ECCurve.java and ECCurve.cs in Bouncy Castle Java (BC Java) before 1.78, BC Java LTS before 2.73.6, BC-FJA before 1.0.2.5, and BC C# .Net before 2.3.1. Importing an EC certificate with crafted F2m parameters can lead to excessive CPU consumption during the evaluation of the curve parameters.
Is GHSA-8xfc-gm6g-vgpv 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 org.bouncycastle:bcprov-jdk18on, and gives you the command that fixes it.
More advisories for org.bouncycastle:bcprov-jdk18on
- HighCVE-2026-13506Bouncy Castle: Lazy ASN.1 sequence forcing resets nesting-depth guard · 3 Aug 2026
- CriticalCVE-2026-8763Bouncy Castle: Name Constraints bypass via trailing dot in rfc822Name and URI · 3 Aug 2026
- CriticalCVE-2025-14813Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks · 17 Apr 2026
- HighCVE-2026-5598Bouncy Castle Has Covert Timing Channel Vulnerability · 17 Apr 2026
- MediumCVE-2026-0636Bouncy Castle has an LDAP injection · 17 Apr 2026
- MediumCVE-2025-8885Bouncy Castle for Java on All (API modules) allows Excessive Allocation · 12 Aug 2025
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2024-29857
- Linkgithub.com/bcgit/bc-csharp/commit/56daa6eac526f165416d17f661422d60de0dfd63
- Linkgithub.com/bcgit/bc-java/commit/efc498ca4caa340ac2fe11f2efee06c1a294501f
- Linkgithub.com/bcgit/bc-java/commit/fee80dd230e7fba132d03a34f1dd1d6aae0d0281
- Linkgithub.com/bcgit/bc-csharp/wiki/CVE%E2%80%902024%E2%80%9029857
- Linkgithub.com/bcgit/bc-java/wiki/CVE%E2%80%902024%E2%80%9029857
- Linksecurity.netapp.com/advisory/ntap-20241206-0008
- Linkwww.bouncycastle.org/latest_releases.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.