GHSA-fjqm-246c-mwqg
In Bouncy Castle JCE Provider the other party DH public key is not fully validated
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.bouncycastle:bcprov-jdk14 | < 1.56 | 1.56 |
| Maven | org.bouncycastle:bcprov-jdk15 | < 1.56 | 1.56 |
| Maven | org.bouncycastle:bcprov-jdk15on | < 1.56 | 1.56 |
Details
As written in the advisory (Markdown source, shown as plain text).
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.
References
External links from the advisory. They lead to third-party sites.
- https://nvd.nist.gov/vuln/detail/CVE-2016-1000346
- https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937
- https://access.redhat.com/errata/RHSA-2018:2669
- https://access.redhat.com/errata/RHSA-2018:2927
- https://github.com/advisories/GHSA-fjqm-246c-mwqg
- https://github.com/bcgit/bc-java
- https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html
- https://security.netapp.com/advisory/ntap-20181127-0004
- https://usn.ubuntu.com/3727-1
- https://www.oracle.com/security-alerts/cpuoct2020.html