Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk18on Maven |
|
|
| org.bouncycastle:bcprov-jdk15on Maven |
|
|
| org.bouncycastle:bcprov-jdk15to18 |
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk18on Maven |
|
|
| org.bouncycastle:bcprov-jdk15on Maven |
|
|
| org.bouncycastle:bcprov-jdk15to18 |
|
|
| org.bouncycastle:bcprov-jdk14 Maven |
|
|
| org.bouncycastle:bctls-jdk18on Maven |
|
|
| org.bouncycastle:bctls-jdk14 Maven |
|
|
| org.bouncycastle:bctls-jdk15to18 Maven |
|
|
| org.bouncycastle:bc-fips Maven |
|
|
| BouncyCastle NuGet |
| No fix yet |
| BouncyCastle.Cryptography NuGet |
|
|
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.
From the CVE record · mitre
Bouncy Castle Java and C# can consume excessive CPU while evaluating curve parameters when importing an EC certificate with crafted F2m parameters. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Check deployments using the listed Maven packages before 1.78, bc-fips before 1.0.2.5, BC Java LTS before 2.73.6, BouncyCastle.Cryptography before 2.3.1, or any version of the NuGet BouncyCastle package.