In Bouncy Castle JCE Provider the other party DH public key is not fully validated
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk14 Maven |
|
|
| org.bouncycastle:bcprov-jdk15 Maven |
|
|
| org.bouncycastle:bcprov-jdk15on Maven |
| Product | Affected | Fixed in |
|---|---|---|
| org.bouncycastle:bcprov-jdk14 Maven |
|
|
| org.bouncycastle:bcprov-jdk15 Maven |
|
|
| org.bouncycastle:bcprov-jdk15on Maven |
|
|
In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation.
From the CVE record · mitre
Bouncy Castle JCE Provider 1.55 and earlier does not fully validate the other party’s Diffie-Hellman public key. Where static Diffie-Hellman is used, an invalid key can reveal details of the other party’s private key. The input does not specify authentication or user-interaction requirements.
Check applications using Maven packages org.bouncycastle:bcprov-jdk14, bcprov-jdk15, or bcprov-jdk15on at versions earlier than 1.56.