CVE-2016-1000339: Medium severity bouncycastle Legion-of-the-bouncy-castle-java-crytography-api vulnerability
Bouncy Castle JCE Provider could allow a remote attacker to obtain sensitive information, caused by a flaw in the AESEngine. An attacker could exploit this vulnerability to obtain sensitive information.
Other sources
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.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2016-1000339.
What is the severity score of CVE-2016-1000339?
CVE-2016-1000339 has a severity score of 5.3, which is considered medium.
What software versions are affected by CVE-2016-1000339?
CVE-2016-1000339 affects Bouncy Castle JCE Provider versions 1.55 and earlier.
How can I fix CVE-2016-1000339?
To fix CVE-2016-1000339, update Bouncy Castle JCE Provider to version 1.56 or later.
Where can I find more information about CVE-2016-1000339?
You can find more information about CVE-2016-1000339 at the following references: [Link 1](https://github.com/bcgit/bc-java/commit/8a73f08931450c17c749af067b6a8185abdfd2c0#diff-494fb066bed02aeb76b6c005632943f2), [Link 2](https://github.com/bcgit/bc-java/commit/413b42f4d770456508585c830cfcde95f9b0e93b#diff-54656f860db94b867ba7542430cd2ef0), [Link 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1588700).