bcpkix-jdk18on is vulnerable to Use of a Broken or Risky Cryptographic Algorithm
63
CVE Score
Medium
Use of a Broken or Risky Cryptographic Algorithm
TSPAlgorithms.ALLOWED includes MD5, and TimeStampToken.validate() accepts a message imprint whose digest is in that set. A time-stamp token can therefore validate with an MD5 imprint. The fix removes MD5 from the default allowed set. TSPAlgorithms.LEGACY and org.bouncycastle.tsp.allowed_imprint_algorithms still allow it.
Upgrade the org.bouncycastle:bcpkix-jdk18on and/or the org.bouncycastle:bcpkix-jdk15to18 library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you validate RFC 3161 time-stamp tokens with TimeStampToken.validate().
1.63 - 1.86
Fixed in 1.87bcpkix-jdk18on is vulnerable to Use of a Broken or Risky Cryptographic Algorithm in versions 1.63 - 1.86.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.