CVE-2018-5382

published 16 Apr 2018 · updated 16 Sep 2024

Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.47.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Legion of the Bouncy Castle>=all <1.471.47

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2018-5382 severity on Zeptric[![CVE-2018-5382](https://zeptric.io/badge/cve/CVE-2018-5382.svg)](https://zeptric.io/cve/CVE-2018-5382)