Page 2 of 13 results (0.006 seconds)

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

13 Dec 2017 — 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." BouncyCastle TLS, en versiones anteriores a la 1.0.3 cuando está configurado para utilizar la JCE (Java Cryptography Extension) para funciones criptográficas, pro... • http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00011.html • CWE-203: Observable Discrepancy •

CVSS: 9.8EPSS: 0%CPEs: 56EXPL: 0

08 Feb 2013 — The TLS implementation in the Bouncy Castle Java library before 1.48 and C# library before 1.8 does not properly consider timing side-channel attacks on a noncompliant MAC check operation during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, a related issue to CVE-2013-0169. La implementación de TLS en la biblioteca Java de Bouncy Castle antes v1.48 y bibliote... • http://openwall.com/lists/oss-security/2013/02/05/24 • CWE-310: Cryptographic Issues CWE-385: Covert Timing Channel •

CVSS: 10.0EPSS: 0%CPEs: 72EXPL: 0

30 Mar 2009 — The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impact and remote attack vectors related to "a Bleichenbacher vulnerability in simple RSA CMS signatures without signed attributes." La Legión de la API de Bouncy Castle Java Cryptography anterior a versión 1.38, como es usada en Crypto Provider Package anterior a versión 1.36, presenta un impacto desconocido y vectores de ataque remoto relacionados con "a Bleichenbacher vul... • http://freshmeat.net/projects/bouncycastlecryptoapi/releases/265580 •