First published: Mon Jun 04 2018(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api | <=1.55 | |
Debian Debian Linux | =8.0 | |
redhat/bouncycastle | <1.56 | 1.56 |
debian/bouncycastle | 1.68-2 1.72-2 1.77-1 | |
IBM GDE | <=3.0.0.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this vulnerability is CVE-2016-1000339.
CVE-2016-1000339 has a severity score of 5.3, which is considered medium.
CVE-2016-1000339 affects Bouncy Castle JCE Provider versions 1.55 and earlier.
To fix CVE-2016-1000339, update Bouncy Castle JCE Provider to version 1.56 or later.
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).