CVE-2017-13098: Observable Discrepancy in BouncyCastle
Summary
CVE-2017-13098: Observable Discrepancy in BouncyCastle. Affects org.bouncycastle:bcprov-jdk15on versions < 1.0.3. Fixed in 1.0.3. How to fix ↓
Also tracked for
- bouncycastle · Debian:11
The same CVE-2017-13098 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 BouncyCastle TLS library is an open-source cryptographic library that provides implementations of various cryptographic algorithms and protocols. It is widely used in Java applications for secure communication. The library includes support for TLS (Transport Layer Security) protocol, which is used to establish secure connections over a network. However, prior to version 1.0.3, when configured to use the JCE (Java Cryptography Extension) for cryptographic functions, BouncyCastle TLS provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. This vulnerability, known as "ROBOT," allows an attacker to recover the private key from a vulnerable application.
Vulnerability Detail
The vulnerability in BouncyCastle TLS allows an attacker to exploit a weak Bleichenbacher oracle and recover the private key from a vulnerable application. This can lead to unauthorized access, data disclosure, and potential compromise of the entire system. The vulnerability is rated as MODERATE severity with a CVSS score of 5.9. It is identified by the CVE identifier CVE-2017-13098 and the alias CVE-2017-13098. The vulnerability was published on 13th May 2022 and reviewed by GitHub on 1st July 2022. The Common Weakness Enumeration (CWE) ID associated with this vulnerability is CWE-203.
How To Fix
Minimum fixed version
1.0.3
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 recommended to apply the fix by upgrading to the latest version of the BouncyCastle TLS library.
Conclusion
The vulnerability in BouncyCastle TLS (CVE-2017-13098) exposes a weak Bleichenbacher oracle, allowing an attacker to recover the private key from a vulnerable application. To mitigate this vulnerability, it is crucial to upgrade to BouncyCastle TLS version 1.0.3 or later. Developers should update their application's dependencies and ensure they are using the fixed version of the library. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.bouncycastle:bcprov-jdk15on →
FAQ
BouncyCastle TLS is an open-source cryptographic library that provides implementations of various cryptographic algorithms and protocols. It is commonly used in Java applications for secure communication.
This vulnerability allows an attacker to recover the private key from a vulnerable application, potentially leading to unauthorized access, data disclosure, and compromise of the system.
To fix this vulnerability, you should upgrade the BouncyCastle TLS library to version 1.0.3 or later. Update your application's dependencies to use the fixed version of the library.
There is no known workaround for this vulnerability. It is recommended to apply the fix by upgrading to the latest version of the BouncyCastle TLS library.
The severity of this vulnerability is rated as MODERATE with a CVSS score of 5.9.
Related vulnerabilities
Recent vulnerabilities recorded for org.bouncycastle:bcprov-jdk15on.
