Timing based private key exposure in Bouncy Castle
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bc-fips Maven |
|
|
| org.bouncycastle:bcprov-ext-jdk15on Maven |
|
|
| org.bouncycastle:bcprov-ext-jdk16 |
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bc-fips Maven |
|
|
| org.bouncycastle:bcprov-ext-jdk15on Maven |
|
|
| org.bouncycastle:bcprov-ext-jdk16 |
|
|
| org.bouncycastle:bcprov-jdk14 Maven |
|
|
| org.bouncycastle:bcprov-jdk15 Maven |
|
|
| org.bouncycastle:bcprov-jdk15on Maven |
|
|
| org.bouncycastle:bcprov-jdk15to18 Maven |
|
|
| org.bouncycastle:bcprov-jdk16 Maven |
|
|
| BouncyCastle NuGet |
|
|
Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
From the CVE record · mitre
The EC math library in affected Bouncy Castle packages has a timing issue. An attacker who can observe timing information from multiple deterministic ECDSA signatures may learn information about the private key. The input does not specify whether authentication or user interaction is required.
Teams using affected Bouncy Castle Java packages before 1.66, the Maven bc-fips package before 1.0.2.1, NuGet BouncyCastle before 1.8.7, or the BC-FJA and BC-FNA versions identified in the advisory should check their deployments.