Bouncy Castle
Approved changes feed: RSS · Atom
cpe:2.3:a:legion_of_the_bouncy_castle:bouncy_castle:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Legion Of The Bouncy Castle (afae62d3-947b-59c5-ae79-df27af9b6f8b) |
|---|---|
| Product | Bouncy Castle (ed972a10-41c0-54de-a6b3-97d14d8836b5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-5382 |
vulnerable | 2026-06-08 05:11:50.704637 |
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 |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.