Bouncy Castle Bouncycastle BC-java

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."

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.

Name Constraints bypass via trailing dot in rfc822Name and URI

MTI/A0 DH agreement exponentiates unvalidated peer value

JSSE hostname verifier CN-fallback enabled by default despite documented opt-in

Stapled OCSP response accepted without binding to the checked certificate

HSS public-key level count unbounded, enabling huge allocation on verify

DTLS handshake reassembler allocates buffer from unchecked 24-bit length

OpenPGP user-attribute subpacket length bounded only by JVM max memory

OER parser recurses without depth limit on self-referential IEEE 1609.2 schema

MLS hash-ratchet honours arbitrary 32-bit generation counter from sender

Quadratic-time escaping when stringifying X.500 distinguished names

Lazy ASN.1 sequence forcing resets nesting-depth guard

OpenPGP CFB quick-check oracle active on symmetric/session-key paths

Possible OOM from unbounded up-front allocation on a definite-length read

MLS wire decoder allocates attacker-declared opaque length before bounds check

CMS verifySignatures returns true for SignedData with zero signers

OpenPGP inline-signature policy failures silently ignored

CCM-family modes write plaintext to caller buffer before tag check

S/MIME validator trusts signer-asserted signingTime for path validation

KCCMBlockCipher MAC does not bind nonce when AAD is absent (cross-nonce AEAD forgery)

CMS AuthenticatedData content not bound to MAC when authAttrs present

IESEngine stream-mode MAC forgery via length-dependent KDF split

OpenPGP AEAD decryption skips final tag on chunk-aligned data

RSA PKCS#1 verification skips last two hash bytes in NULL-omitted path

CMS AuthEnvelopedData fails to enforce tag-length on decryption

BKS/UBER keystore allocates from untrusted lengths before integrity check

ML-KEM (Kyber) decapsulation leaks private key information through non-constant-time division in message decoding and ciphertext compression (KyberSlash)

PKCS#8 / PBES2 decryptors honour unbounded KDF cost from input

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.

BouncyCastle JCE TLS Bleichenbacher/ROBOT

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.

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.

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 passing parameters to the key pair generator.

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 general usage) spurious calculations for elliptic curve scalar multiplications. Such errors would have been detected with high probability by the output validation for our scalar multipliers.

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.

PKCS#12 MAC and bag-decryption KDF iteration-count bound (DoS)

BKS keystore accepts legacy version with 16-bit integrity MAC key

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.

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.