CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2016-1000338 – bouncycastle: DSA does not fully validate ASN.1 encoding during signature verification allowing for injection of unsigned data
https://notcve.org/view.php?id=CVE-2016-1000338
01 Jun 2018 — In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure. En Bouncy Castle JCE Provider en versiones 1.55 y anteriores, el DSA no valida completamente el cifrado ASN.1 de la firma en verificación. Es posible inyectar elementos extra en la... • https://access.redhat.com/errata/RHSA-2018:2669 • CWE-325: Missing Cryptographic Step CWE-347: Improper Verification of Cryptographic Signature •
CVSS: 5.1EPSS: 0%CPEs: 3EXPL: 0CVE-2018-5382 – Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions
https://notcve.org/view.php?id=CVE-2018-5382
16 Apr 2018 — The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type "BKS-V1" was introduced in 1.49. It should be noted that the use of "BKS-V1" is discouraged by the library authors and... • http://www.securityfocus.com/bid/103453 • CWE-327: Use of a Broken or Risky Cryptographic Algorithm CWE-354: Improper Validation of Integrity Check Value •
CVSS: 7.5EPSS: 76%CPEs: 1EXPL: 0CVE-2017-13098 – BouncyCastle JCE TLS Bleichenbacher/ROBOT
https://notcve.org/view.php?id=CVE-2017-13098
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: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2016-2427
https://notcve.org/view.php?id=CVE-2016-2427
18 Apr 2016 — The AES-GCM specification in RFC 5084, as used in Android 5.x and 6.x, recommends 12 octets for the aes-ICVlen parameter field, which might make it easier for attackers to defeat a cryptographic protection mechanism and discover an authentication key via a crafted application, aka internal bug 26234568. NOTE: The vendor disputes the existence of this potential issue in Android, stating "This CVE was raised in error: it referred to the authentication tag size in GCM, whose default according to ASN.1 encoding... • http://source.android.com/security/bulletin/2016-04-02.html • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 9.8EPSS: 1%CPEs: 12EXPL: 0CVE-2015-7940 – bouncycastle: Invalid curve attack allowing to extract private keys
https://notcve.org/view.php?id=CVE-2015-7940
09 Nov 2015 — The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an "invalid curve attack." La librería Bouncy Castle Java en versiones anteriores a 1.51 no valida un punto que se encuentra dentro de la curva elíptica, lo que facilita a atacantes remotos obtener claves privadas a través de una serie de intercambios de clave de cu... • http://lists.fedoraproject.org/pipermail/package-announce/2016-January/174915.html • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-310: Cryptographic Issues CWE-358: Improperly Implemented Security Check for Standard •
CVSS: 9.8EPSS: 0%CPEs: 56EXPL: 0CVE-2013-1624 – bouncycastle: TLS CBC padding timing attack
https://notcve.org/view.php?id=CVE-2013-1624
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: 0CVE-2007-6721
https://notcve.org/view.php?id=CVE-2007-6721
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 •