CVE-2016-1000339: Vulnerability in org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
Summary
CVE-2016-1000339: In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Affects org.bouncycastle:bcprov-jdk14 versions < 1.56. Fixed in 1.56. How to fix ↓
Also tracked for
- bouncycastle · Debian:11
The same CVE-2016-1000339 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 packages are part of the Bouncy Castle Java Cryptography API, which provides a wide range of cryptographic algorithms. These packages include an implementation of the AES (Advanced Encryption Standard) algorithm. AESFastEngine was the primary engine class used for AES in versions 1.55 and earlier. However, it was discovered that the table-driven approach used in AESFastEngine could leak information about the AES key being used if the data channel on the CPU is monitored. AESEngine also had a lesser leakage issue. To address these vulnerabilities, AESEngine has been modified to remove any signs of leakage and is now the primary AES class starting from version 1.56. The use of AESFastEngine is now only recommended where otherwise deemed appropriate.
Vulnerability Detail
The vulnerability in org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 arises from the leakage of information about the AES key being used in the AESFastEngine class. This leakage can occur if the data channel on the CPU is monitored. The AESFastEngine class uses a highly table-driven approach, and the lookup table accesses can be observed to infer the AES key. AESEngine also had a leakage issue, although it was less severe. The impact of this vulnerability is that an attacker with access to the data channel on the CPU could potentially obtain the AES key being used, compromising the confidentiality of encrypted data. The vulnerability has a CVSS score of 5.3 (Moderate severity).
How To Fix
Latest published version: 1.86 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.56
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. The recommended approach is to update to the fixed version of the packages.
Conclusion
The org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 packages are vulnerable to a leakage issue in the AESFastEngine class, which can potentially expose the AES key being used. To mitigate this vulnerability, it is recommended to update to version 1.56 or later of the packages. No specific workaround is available. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for org.bouncycastle:bcprov-jdk14 →
FAQ
The vulnerability allows an attacker to potentially obtain the AES key being used, compromising the confidentiality of encrypted data.
Versions 1.55 and earlier are affected. The vulnerability is fixed in version 1.56 and later.
No specific workaround is mentioned. It is recommended to update to the fixed version of the packages.
The CVSS score of this vulnerability is 5.3, indicating a Moderate severity.
You can find more information about this vulnerability in the GitHub Advisory Database: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2018/10/GHSA-c8xf-m4ff-jcxj/GHSA-c8xf-m4ff-jcxj.json
References
Related vulnerabilities
Recent vulnerabilities recorded for org.bouncycastle:bcprov-jdk14.
