CVE-2016-1000346
Published: 4 June 2018
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.
Priority
Status
Package | Release | Status |
---|---|---|
bouncycastle Launchpad, Ubuntu, Debian |
artful |
Not vulnerable
(1.57-1)
|
bionic |
Not vulnerable
(1.59-1)
|
|
cosmic |
Not vulnerable
(1.60-1)
|
|
disco |
Not vulnerable
(1.60-1)
|
|
eoan |
Not vulnerable
(1.60-1)
|
|
focal |
Not vulnerable
(1.60-1)
|
|
groovy |
Not vulnerable
(1.60-1)
|
|
hirsute |
Not vulnerable
(1.60-1)
|
|
impish |
Not vulnerable
(1.60-1)
|
|
jammy |
Not vulnerable
(1.60-1)
|
|
precise |
Does not exist
|
|
trusty |
Does not exist
(trusty was released [1.49+dfsg-2ubuntu0.1])
|
|
upstream |
Released
(1.56-1)
|
|
xenial |
Needed
|
|
Patches: upstream: https://github.com/bcgit/bc-java/commit/1127131c89021612c6eefa26dbe5714c194e7495 |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 3.7 |
Attack vector | Network |
Attack complexity | High |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | Low |
Integrity impact | None |
Availability impact | None |
Vector | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |