Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| artful | not-affected | 1.57-1 |
| bionic | not-affected | 1.59-1 |
| cosmic | not-affected | 1.60-1 |
| devel | not-affected | 1.60-1 |
| disco | not-affected | 1.60-1 |
| eoan | not-affected | 1.60-1 |
| esm-apps-legacy/xenial | needed | |
| esm-apps/bionic | not-affected | 1.59-1 |
| esm-apps/focal | not-affected | 1.60-1 |
| esm-apps/jammy | not-affected | 1.60-1 |
Показывать по
EPSS
4.3 Medium
CVSS2
3.7 Low
CVSS3
Связанные уязвимости
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.
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.
In the Bouncy Castle JCE Provider version 1.55 and earlier the other p ...
In Bouncy Castle JCE Provider the other party DH public key is not fully validated
EPSS
4.3 Medium
CVSS2
3.7 Low
CVSS3