cpe:/a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api:1.55 cpe:/o:debian:debian_linux:8.0 CVE-2016-1000346 2018-06-04T17:29:00.303-04:00 2018-11-28T06:29:01.563-05:00 4.3 NETWORK MEDIUM NONE PARTIAL NONE NONE http://nvd.nist.gov 2018-07-16T09:29:54.743-04:00 REDHAT RHSA-2018:2669 REDHAT RHSA-2018:2927 UBUNTU USN-3727-1 MLIST [debian-lts-announce] 20180707 [SECURITY] [DLA 1418-1] bouncycastle security update CONFIRM https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937 CONFIRM https://security.netapp.com/advisory/ntap-20181127-0004/ 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.