Vulnerabilities · 2016 · Bouncycastle
CVE-2016-1000339
Bouncycastle Bc-java vulnerability
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.
Affected products
Bc-java, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Bouncycastle Bc-java runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db9 · Patch
- github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed0 · Patch
- lists.debian.org/debian-lts-announce/2018/07/msg00009.html · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2669
- access.redhat.com/errata/RHSA-2018:2927
- security.netapp.com/advisory/ntap-20181127-0004/
- usn.ubuntu.com/3727-1/
- www.oracle.com/security-alerts/cpuoct2020.html
- nvd.nist.gov/vuln/detail/CVE-2016-1000339
- cve.org/CVERecord?id=CVE-2016-1000339
More vulnerabilities in Bouncycastle products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.