CVE-2016-1000339
Published: 4 June 2018
In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now the primary AES class for the BC JCE provider from 1.56. Use of AESFastEngine is now only recommended where otherwise deemed appropriate.
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)
|
|
| kinetic |
Not vulnerable
(1.60-1)
|
|
| lunar |
Not vulnerable
(1.60-1)
|
|
| trusty |
Released
(1.49+dfsg-2ubuntu0.1)
|
|
| upstream |
Released
(1.56-1)
|
|
| xenial |
Needed
|
|
|
Patches: upstream: https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b upstream: https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0 |
||
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 5.3 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | Low |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |