In Bouncy Castle JCE Provider the other party DH public key is not fully validated
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-1000346US | low3.7 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2018:2669WEB
- https://access.redhat.com/errata/RHSA-2018:2927WEB
- https://github.com/advisories/GHSA-fjqm-246c-mwqgADVISORY
- https://github.com/bcgit/bc-javaPACKAGE
- https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937WEB
- https://lists.debian.org/debian-lts-announce/2018/07/msg00009.htmlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000346ADVISORY
- https://security.netapp.com/advisory/ntap-20181127-0004WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan