First published: Mon Jun 04 2018(Updated: )
Bouncy Castle JCE Provider could provide weaker than expected security, caused by an environment where timings can be easily observed. A remote attacker could exploit this vulnerability to conduct a padding oracle attack.
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 is CVE-2016-1000345.
The severity level of CVE-2016-1000345 is medium, with a severity value of 5.9.
The Bouncy Castle JCE Provider version 1.55 and earlier is affected by CVE-2016-1000345.
To fix the vulnerability CVE-2016-1000345, update to Bouncy Castle JCE Provider version 1.56 or later.
Yes, you can find additional information about CVE-2016-1000345 at the following references: [Reference 1](https://github.com/bcgit/bc-java/commit/21dcb3d9744c83dcf2ff8fcee06dbca7bfa4ef35#diff-4439ce586bf9a13bfec05c0d113b8098), [Reference 2](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1588325), [Reference 3](https://access.redhat.com/security/updates/classification/).