20 results (0.013 seconds)

CVSS: 7.8EPSS: 0%CPEs: 3EXPL: 0

09 May 2024 — An issue was discovered in Bouncy Castle Java Cryptography APIs before 1.78. An Ed25519 verification code infinite loop can occur via a crafted signature and public key. Se descubrió un problema en las API de criptografía Java de Bouncy Castle anteriores a la versión 1.78. Se puede producir un bucle infinito del código de verificación Ed25519 mediante una firma manipulada y una clave pública. A flaw was found in the Bouncy Castle Java Cryptography APIs. • https://security.netapp.com/advisory/ntap-20240614-0007 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •

CVSS: 8.1EPSS: 6%CPEs: 39EXPL: 3

18 Dec 2020 — An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password, allowing incorrect passwords to indicate they were matching with previously hashed ones that were different. Se detectó un problema en Legion of the Bouncy Castle BC Java versiones 1.65 y 1.66. El método de la utilidad OpenBSDBCrypt.checkPassword comparó datos incorrectos al comprobar la contraseña, permitiendo a unas contraseña... • https://github.com/madstap/bouncy-castle-generative-test-poc • CWE-287: Improper Authentication •

CVSS: 7.5EPSS: 13%CPEs: 34EXPL: 0

08 Oct 2019 — The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data. This is fixed in 1.64. El analizador ASN.1 en Bouncy Castle Crypto (también se conoce como BC Java) versión 1.63, puede desencadenar un intento de asignación de memoria grande y un error OutOfMemoryError resultante, por medio de datos ASN.1 diseñados. Esto se corrige en la versión 1.64. • https://lists.apache.org/thread.html/r02f887807a49cfd1f1ad53f7a61f3f8e12f60ba2c930bec163031209%40%3Ccommits.tomee.apache.org%3E • CWE-770: Allocation of Resources Without Limits or Throttling •

CVSS: 9.8EPSS: 4%CPEs: 47EXPL: 0

09 Jul 2018 — 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 pic... • http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00011.html • CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') •

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

05 Jun 2018 — 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. Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 y anteriores tiene un vulnerabilidad en la interfaz de bajo nivel del generador de claves RSA; específicamente, los par... • http://www.securityfocus.com/bid/106567 • CWE-325: Missing Cryptographic Step CWE-327: Use of a Broken or Risky Cryptographic Algorithm •

CVSS: 5.9EPSS: 1%CPEs: 2EXPL: 0

04 Jun 2018 — In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding. En Bouncy Castle JCE Provider, en versiones 1.55 y anteriores, el modo DHIES/ECIES CBC es vulnerable a ataques de oráculo de relleno. Para BC 1.55 y anteriores, en un entorno en el que las sincronizaciones pueden ... • https://access.redhat.com/errata/RHSA-2018:2669 • CWE-325: Missing Cryptographic Step CWE-361: 7PK - Time and State •

CVSS: 4.8EPSS: 1%CPEs: 2EXPL: 0

04 Jun 2018 — In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation. En Bouncy Castle JCE Provider, en versiones 1.55 y anteriores, no se valida completamente la clave pública DH de la otra parte. Esto puede causar problemas, ya que las claves invál... • https://access.redhat.com/errata/RHSA-2018:2669 • CWE-320: Key Management Errors CWE-325: Missing Cryptographic Step •

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

04 Jun 2018 — In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider. En la versión 1.55 y anteriores de Bouncy Castle JCE Provider, la implementación ECIES permitía el uso del modo ECB. Este modo se considera inseguro y el fabricante le ha retirado el soporte. Red Hat Fuse, based on Apache ServiceMix, provides a small-footprint, flexible, open source enterprise service bus and i... • https://access.redhat.com/errata/RHSA-2018:2669 • CWE-310: Cryptographic Issues CWE-325: Missing Cryptographic Step •

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

04 Jun 2018 — In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider. En la versión 1.55 y anteriores de Bouncy Castle JCE Provider, la implementación DHIES permitía el uso del modo ECB. Este modo se considera inseguro y el fabricante le ha retirado el soporte. Red Hat Fuse, based on Apache ServiceMix, provides a small-footprint, flexible, open source enterprise service bus and i... • https://access.redhat.com/errata/RHSA-2018:2669 • CWE-310: Cryptographic Issues CWE-325: Missing Cryptographic Step •

CVSS: 5.3EPSS: 1%CPEs: 2EXPL: 0

04 Jun 2018 — In the Bouncy Castle JCE Provider version 1.55 and earlier the primary engine class used for AES was AESFastEngine. Due to the highly table driven approach used in the algorithm it turns out that if the data channel on the CPU can be monitored the lookup table accesses are sufficient to leak information on the AES key being used. There was also a leak in AESEngine although it was substantially less. AESEngine has been modified to remove any signs of leakage (testing carried out on Intel X86-64) and is now t... • https://access.redhat.com/errata/RHSA-2018:2669 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-310: Cryptographic Issues •