Debian Bouncycastle vulnerabilities

CVE-2014-3566 [LOW] CVE-2014-3566: bouncycastle - The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses... The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the "POODLE" issue. Scope: local bookworm: resolved bullseye: resolved forky: resolved sid: resolved trixie: resolved

CVE-2011-3389 [MEDIUM] CVE-2011-3389: asterisk - The SSL protocol, as used in certain configurations in Microsoft Windows and Mic... The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS s

CVE-2020-28052 [HIGH] CVE-2020-28052: bouncycastle - An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. Th... 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. Scope: local bookworm: resolved (fixed in 1.65-2) bullseye: resolved (fixed i

CVE-2018-1000613 [CRITICAL] CVE-2018-1000613: bouncycastle - Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1... 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 ex

CVE-2017-13098 [HIGH] CVE-2017-13098: bouncycastle - BouncyCastle TLS prior to version 1.0.3, when configured to use the JCE (Java Cr... 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." Scope: local

CVE-2018-1000180 [HIGH] CVE-2018-1000180: bouncycastle - Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw... 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. Scope: local bookworm:

CVE-2016-1000343 [HIGH] CVE-2016-1000343: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair gene... In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly pass

CVE-2024-34447 [HIGH] CVE-2024-34447: bouncycastle - An issue was discovered in the Bouncy Castle Crypto Package For Java before BC T... An issue was discovered in the Bouncy Castle Crypto Package For Java before BC TLS Java 1.0.19 (ships with BC Java 1.78, BC Java (LTS) 2.73.6) and before BC FIPS TLS Java 1.0.19. When endpoint identification is enabled in the BCJSSE and an SSL socket is created without an explicit hostname (as happens with HttpsURLConnection), hostname verification could be per

CVE-2016-1000352 [HIGH] CVE-2016-1000352: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementat... 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. Scope: local bookworm: resolved (fixed in 1.56-1) bullseye: resolved (fixed in 1.56-1) forky: resolved (fixed in 1.56-1) sid: resolved (fixed in 1.56-1) trixie

CVE-2016-1000344 [HIGH] CVE-2016-1000344: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementat... 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. Scope: local bookworm: resolved (fixed in 1.56-1) bullseye: resolved (fixed in 1.56-1) forky: resolved (fixed in 1.56-1) sid: resolved (fixed in 1.56-1) trixie

CVE-2016-1000338 [HIGH] CVE-2016-1000338: bouncycastle - In Bouncy Castle JCE Provider version 1.55 and earlier the DSA does not fully va... 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. Scope: local bookworm: reso

CVE-2016-1000342 [HIGH] CVE-2016-1000342: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully ... In the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA 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. Scope: local bookworm: re

CVE-2024-29857 [HIGH] CVE-2024-29857: bouncycastle - An issue was discovered in ECCurve.java and ECCurve.cs in Bouncy Castle Java (BC... An issue was discovered in ECCurve.java and ECCurve.cs in Bouncy Castle Java (BC Java) before 1.78, BC Java LTS before 2.73.6, BC-FJA before 1.0.2.5, and BC C# .Net before 2.3.1. Importing an EC certificate with crafted F2m parameters can lead to excessive CPU consumption during the evaluation of the curve parameters. Scope: local bookworm: open bullseye: open

CVE-2016-1000340 [HIGH] CVE-2016-1000340: bouncycastle - In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug... In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for several raw math classes have been fixed (org.bouncycastle.math.raw.Nat???). These classes are used by our custom elliptic curve implementations (org.bouncycastle.math.ec.custom.**), so there was the possibility of rare (in g

CVE-2024-30172 [HIGH] CVE-2024-30172: bouncycastle - An issue was discovered in Bouncy Castle Java Cryptography APIs before 1.78. An ... 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. Scope: local bookworm: open bullseye: open forky: resolved (fixed in 1.80-1) sid: resolved (fixed in 1.80-1) trixie: resolved (fixed in 1.80-1)

CVE-2025-8885 [MEDIUM] CVE-2025-8885: bouncycastle - Allocation of Resources Without Limits or Throttling vulnerability in Legion of ... Allocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BC-FJA bc-fips on All allows Excessive Allocation. This vulnerability is associated with program files https://github.com/bcgit/bc-java/blob/main/core/src/main/java/org/bouncycastle/asn1/ASN

CVE-2007-6721 [CRITICAL] CVE-2007-6721: bouncycastle - The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as us... 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." Scope: local bookworm: resolved (fixed in 1.38-1) bullseye: resolved (fixed in 1.38-1) forky:

CVE-2025-8916 [MEDIUM] CVE-2025-8916: bouncycastle - Allocation of Resources Without Limits or Throttling vulnerability in Legion of ... Allocation of Resources Without Limits or Throttling vulnerability in Legion of the Bouncy Castle Inc. BC Java bcpkix on All (API modules), Legion of the Bouncy Castle Inc. BC Java bcprov on All (API modules), Legion of the Bouncy Castle Inc. BCPKIX FIPS bcpkix-fips on All (API modules) allows Excessive Allocation. This vulnerability is associated with program

CVE-2013-0169 [LOW] CVE-2013-0169: bouncycastle - The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenS... The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical anal

CVE-2016-1000345 [MEDIUM] CVE-2016-1000345: bouncycastle - In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC m... 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. Scope: local bookworm: resolved (fixed in 1.56-1) bullseye