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.
Weaknesses in this category are related to the design and implementation of data confidentiality and integrity. Frequently these deal with the use of encoding techniques, encryption libraries, and hashing algorithms. The weaknesses in this category could lead to a degradation of the quality data if they are not addressed.
| Link | Tags |
|---|---|
| https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html | third party advisory mailing list |
| https://access.redhat.com/errata/RHSA-2018:2669 | vendor advisory |
| https://usn.ubuntu.com/3727-1/ | vendor advisory |
| https://access.redhat.com/errata/RHSA-2018:2927 | vendor advisory |
| https://www.oracle.com/security-alerts/cpuoct2020.html | |
| https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2 | third party advisory patch |
| https://security.netapp.com/advisory/ntap-20181127-0004/ | |
| https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0 | third party advisory patch |