Approved changes feed: RSS · Atom
cpe:2.3:a:bouncycastle:bc-java:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Bouncycastle (8993aee6-be06-52a7-a5ab-9d1fe290e16e) |
|---|---|
| Product | Bc Java (304e581d-ef3b-5ff2-bb26-375fdd3115f3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/bcgit/bc-java |
purl2cpe | 2026-06-01 10:12:20.989121 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-29857 |
vulnerable | 2026-06-08 06:33:29.453735 |
Details available
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.
Published: 2024-05-09T04:17:29.645Z
Updated: 2025-02-13T15:47:48.325Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-33201 |
vulnerable | 2026-06-08 06:06:21.990387 |
Details available
Bouncy Castle For Java before 1.74 is affected by an LDAP injection vulnerability. The vulnerability only affects applications that use an LDAP CertStore from Bouncy Castle to validate X.509 certificates. During the certificate validation process, Bouncy Castle inserts the certificate's Subject Name into an LDAP search filter without any escaping, which leads to an LDAP injection vulnerability.
Published: 2023-07-05T00:00:00.000Z
Updated: 2024-12-04T15:48:15.487Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-5382 |
vulnerable | 2026-06-08 05:11:50.707930 |
Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions
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 should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself.
Published: 2018-04-16T13:00:00.000Z
Updated: 2024-09-16T16:27:56.228Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-1000613 |
vulnerable | 2026-06-08 05:10:25.839256 |
Details available
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.
Published: 2018-07-09T20:00:00.000Z
Updated: 2024-11-14T20:37:00.531Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-1000180 |
vulnerable | 2026-06-08 05:10:25.608146 |
Details available
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.
Published: 2018-06-05T13:00:00.000Z
Updated: 2024-08-05T12:33:49.372Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-13098 |
vulnerable | 2026-06-08 05:08:48.447865 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000352 |
vulnerable | 2026-06-08 05:07:16.941067 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000346 |
vulnerable | 2026-06-08 05:07:16.940501 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000345 |
vulnerable | 2026-06-08 05:07:16.940097 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000344 |
vulnerable | 2026-06-08 05:07:16.939697 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000343 |
vulnerable | 2026-06-08 05:07:16.939355 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000342 |
vulnerable | 2026-06-08 05:07:16.938894 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000341 |
vulnerable | 2026-06-08 05:07:16.938471 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000340 |
vulnerable | 2026-06-08 05:07:16.938020 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2016-1000339 |
vulnerable | 2026-06-08 05:07:16.937537 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2007-6721 |
vulnerable | 2026-06-08 04:50:09.622139 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.