CVE-2016-1000341: Timing Attack Vulnerability in org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15
Summary
CVE-2016-1000341: In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. 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-1000341 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 Extension (JCE) Provider. These packages provide cryptographic algorithms and utilities for secure communication and data protection. The vulnerability identified as CVE-2016-1000341 affects versions 1.55 and earlier of the Bouncy Castle JCE Provider. This vulnerability specifically impacts the generation of DSA signatures, where the lack of blinding in these versions allows an attacker to observe timings and potentially gain information about the signature's k value and the private value as well.
Vulnerability Detail
The timing attack vulnerability in org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 arises from the absence of blinding in version 1.55 and earlier of the Bouncy Castle JCE Provider. By closely observing the timings during signature generation, an attacker can exploit this vulnerability to infer the signature's k value and potentially deduce the private value. This information disclosure can lead to the compromise of cryptographic keys and the integrity of the system.
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 known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the fixed version of the Bouncy Castle JCE Provider.
Conclusion
The timing attack vulnerability in org.bouncycastle:bcprov-jdk14 and org.bouncycastle:bcprov-jdk15 can be mitigated by upgrading to version 1.56 or later of the Bouncy Castle JCE Provider. It is crucial to promptly apply this fix to prevent potential information disclosure and compromise of cryptographic keys. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.bouncycastle:bcprov-jdk14 →
FAQ
The vulnerability allows an attacker to gain information about the private value used in DSA signature generation. This can lead to the compromise of cryptographic keys and the integrity of the system.
Versions 1.55 and earlier of the Bouncy Castle JCE Provider are vulnerable to this timing attack.
There are no known public exploits for this vulnerability at the time of this report.
Yes, upgrading to version 1.56 or later of the Bouncy Castle JCE Provider fixes this vulnerability.
Regenerating cryptographic keys is recommended to ensure their integrity after applying the fix for this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for org.bouncycastle:bcprov-jdk14.
