CVE-2016-1000339

Published: 04 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

Medium

CVSS 3 base score: 5.3

Status

Package Release Status
bouncycastle
Launchpad, Ubuntu, Debian
Upstream
Released (1.56-1)
Ubuntu 21.10 (Impish Indri) Not vulnerable
(1.60-1)
Ubuntu 21.04 (Hirsute Hippo) Not vulnerable
(1.60-1)
Ubuntu 20.04 LTS (Focal Fossa) Not vulnerable
(1.60-1)
Ubuntu 18.04 LTS (Bionic Beaver) Not vulnerable
(1.59-1)
Ubuntu 16.04 ESM (Xenial Xerus) Ignored
(end of standard support, was needed)
Ubuntu 14.04 ESM (Trusty Tahr) Does not exist
(trusty was released [1.49+dfsg-2ubuntu0.1])
Patches:
Upstream: https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b
Upstream: https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0