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
Configurations
History
21 Nov 2024, 02:43
Type | Values Removed | Values Added |
---|---|---|
References | () https://access.redhat.com/errata/RHSA-2018:2669 - | |
References | () https://access.redhat.com/errata/RHSA-2018:2927 - | |
References | () https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495#diff-d525a20b8acaed791ae2f0f770eb5937 - Patch, Third Party Advisory | |
References | () https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html - Third Party Advisory | |
References | () https://security.netapp.com/advisory/ntap-20181127-0004/ - | |
References | () https://usn.ubuntu.com/3727-1/ - | |
References | () https://www.oracle.com/security-alerts/cpuoct2020.html - |
Information
Published : 2018-06-04 21:29
Updated : 2024-11-21 02:43
NVD link : CVE-2016-1000346
Mitre link : CVE-2016-1000346
CVE.ORG link : CVE-2016-1000346
JSON object : View
Products Affected
debian
- debian_linux
bouncycastle
- legion-of-the-bouncy-castle-java-crytography-api
CWE
CWE-320
Key Management Errors