Описание
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.
Отчет
This issue affects the versions of bouncycastle as shipped with Red Hat Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having a security impact of Moderate. No update is planned for this product at this time. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| JBoss Developer Studio 11 | bouncycastle | Not affected | ||
| Red Hat JBoss Data Grid 7 | bouncycastle | Not affected | ||
| Red Hat JBoss Data Virtualization 6 | bouncycastle | Out of support scope | ||
| Red Hat JBoss Enterprise Application Platform 7 | bouncycastle | Not affected | ||
| Red Hat JBoss Fuse 6 | bouncycastle | Will not fix | ||
| Red Hat JBoss Fuse Integration Service 2 | bouncycastle | Not affected | ||
| Red Hat OpenShift Application Runtimes | bouncycastle | Not affected | ||
| Red Hat Single Sign-On 7 | bouncycastle | Not affected | ||
| Red Hat Software Collections | rh-eclipse46-bouncycastle | Will not fix | ||
| Red Hat Subscription Asset Manager | bouncycastle | Will not fix |
Показывать по
Дополнительная информация
Статус:
EPSS
4.8 Medium
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.8 Medium
CVSS3