CVE-2023-33201

CVE-2023-33201 relates to Bouncy Castle for Java (bc-java) before 1.74, where LDAP injection can occur during X.509 cert validation when an LDAP CertStore is used. The vacuum is created by inserting the certificate’s Subject Name into an LDAP search filter without escaping, enabling LDAP injectio...

CVE-2020-28052

CVE-2020-28052 — BC Java OpenBSDBCrypt.password check issue : In Legion of the Bouncy Castle BC Java versions 1.65 and 1.66, the OpenBSDBCrypt.checkPassword method can compare data incorrectly during password verification, causing some incorrect passwords to be treated as a match for different, p...

CVE-2018-1000613

CVE-2018-1000613 concerns Legion of the Bouncy Castle Java Cryptography APIs (BC) 1.58–1.59 up to, but not including, 1.60. It is a CWE-470 Unsafe Reflection vulnerability in XMSS/XMSS^MT private key deserialization, which can allow a remote attacker to execute arbitrary code by crafting a privat...

CVE-2018-1000180

CVE-2018-1000180 affects Bouncy Castle BC 1.54–1.59 (and BC-FJA 1.0.0/1.0.1) with a flaw in the Low-level RSA key pair generator interface that may produce RSA key pairs with fewer Miller–Rabin primality tests than expected. IBM vulnerability bulletins associate this CVE with IBM products (e.g., ...

CVE-2017-13098

Bouncy Castle TLS prior to 1.0.3, when configured to use the JCE for cryptographic operations, is vulnerable to a Bleichenbacher/ROBOT oracle when RSA key exchange is negotiated. An attacker could use this to recover the private key from a vulnerable application. Affected: Bouncy Castle TLS (Java...

CVE-2019-17359

The CVE-2019-17359 entry concerns Bouncy Castle Crypto (BC Java) 1.63. The vulnerability lies in the ASN.1 parser, which can trigger a large memory allocation leading to a memory exhaustion/OutOfMemoryError via crafted ASN.1 data. Affected product: BC Java 1.63; fixed in BC Java 1.64. The issue i...

CVE-2016-1000339

CVE-2016-1000339 describes a cryptographic leakage in Bouncy Castle JCE Provider v1.55 and earlier, where the primary AES engine class was AESFastEngine. Because of the table-driven lookup, data channel timing could leak information about the AES key via table accesses; AESEngine also had leaks b...

CVE-2018-5382

CVE-2018-5382 involves Bouncy Castle where the default BKS keystore uses an HMAC only 16 bits long, enabling brute-force attempts to compromise keystore integrity. Technical details from connected docs show that BC 1.47 updated the BKS format to use a 160-bit HMAC, addressing the issue for keysto...

CVE-2016-1000343

CVE-2016-1000343 affects the Bouncy Castle JCE Provider (1.55 and earlier). When the JCA key pair generator is not explicitly initialised with DSA parameters, it may generate a weak private key by assuming a 1024-bit key size. Publicly available documents confirm this issue and recommend either e...

CVE-2016-1000345

CVE-2016-1000345 (padding oracle in Bouncy Castle JCE Provider DHIES/ECIES CBC) affects BC 1.55 and earlier; in environments with observable timings, decryption padding failures can be inferred via timing analyses. The IBM/BC-focused bulletin confirms this CVE among multiple BC-related issues and...

CVE-2016-1000342

CVE-2016-1000342 is associated with Bouncy Castle JCE Provider up to version 1.55 and earlier, where ECDSA does not fully validate ASN.1 encoding of signatures during verification. This can allow injection of extra elements in the signature sequence and may permit the introduction of “invisible” ...

CVE-2016-1000346

CVE-2016-1000346 is a vulnerability in the Bouncy Castle JCE Provider where, in version 1.55 and earlier, the other party's DH public key was not fully validated during Diffie-Hellman key exchange, enabling potential leakage of private key details. Release 1.56 added parameter checks on the agree...

CVE-2016-1000344

CVE-2016-1000344 : The vulnerability stems from the DHIES implementation in the Bouncy Castle JCE Provider (versions 1.55 and earlier) allowing ECB mode. IBM security bulletins note this BC vulnerability affecting IBM Sterling products (e.g., Sterling File Gateway and Sterling B2B Integrator) and...

CVE-2016-1000341

CVE-2016-1000341 : The Bouncy Castle JCE Provider (BC-JCE) up to version 1.55 and earlier suffers a timing-side-channel in DSA signature generation. The lack of blinding can allow an observer to deduce the signature’s k value, potentially leaking the private key. The vulnerability is tied to the ...

CVE-2013-1624

Technical details for CVE-2013-1624 are not publicly available in the provided documents. Monitor for updates.

CVE-2016-1000352

In CVE-2016-1000352, the Bouncy Castle JCE Provider (BC) up to version 1.55 allowed ECB mode in ECIES, which is insecure. Affected product: BC JCE Provider

CVE-2016-1000340

The CVE-2016-1000340 issue describes a carry propagation bug in the Bouncy Castle JCE Provider (versions 1.51–1.55) affecting the squaring path of several Nat-based raw math classes used by custom EC implementations. This could cause rare, spurious calculations during elliptic-curve scalar multip...

CVE-2007-6721

CVE-2007-6721 concerns the Legion of the Bouncy Castle Java Cryptography API (used in Crypto Provider Package) up to release 1.38; a Bleichenbacher vulnerability affects simple RSA CMS signatures without signed attributes. The exact impact is described as unknown in some sources, with remote atta...

CVE-2016-2427

The CVE-2016-2427 entry concerns AES-GCM-ICVlen = 12 octets in the AES-GCM implementation used by Android 5.x–6.x. The NVD description cites a potential weakness that could defeat cryptographic protection and reveal an authentication key via a crafted app. However, Android’s vendor notes state th...