CPE Details
Bouncy Castle Legion-of-the-bouncy-castle-java-crytography-api 1.58
1.58
2018-10-15
14h19 +00:00
14h19 +00:00
2018-10-15
14h19 +00:00
14h19 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api:1.58:*:*:*:*:*:*:*
Informations
Vendor
bouncycastleProduct
legion-of-the-bouncy-castle-java-crytography-apiVersion
1.58Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
| Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in XMSS/XMSS^MT private key deserialization that can result in Deserializing an XMSS/XMSS^MT private key can result in the execution of unexpected code. This attack appear to be exploitable via A handcrafted private key can include references to unexpected classes which will be picked up from the class path for the executing application. This vulnerability appears to have been fixed in 1.60 and later. | 9.8 |
Critical |
||
| Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-level API with added certainty may have less M-R tests than expected. This appears to be fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later. | 7.5 |
High |
||
| BouncyCastle TLS prior to version 1.0.3, when configured to use the JCE (Java Cryptography Extension) for cryptographic functions, provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a vulnerable application. This vulnerability is referred to as "ROBOT." | 7.5 |
High |
2025©
tesweb SA
