What’s Vulnerable › Vulnerabilities
CVE-2018-5382: Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions
- Severity: medium (CVSS 4.4 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2018-04-16 · updated 2026-06-17
- Weakness: CWE-327
Description
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 products
- Legion of the Bouncy Castle Inc. BC-JAVA: through 1.49
- Red Hat Satellite 6: 6.4
- RedHat Satellite Capsule: 6.4
References
- http://www.securityfocus.com/bid/103453
- https://access.redhat.com/errata/RHSA-2018:2927
- https://www.bouncycastle.org/releasenotes.html
- https://www.kb.cert.org/vuls/id/306792
- https://www.oracle.com/security-alerts/cpuoct2020.html
- http://www.securityfocus.com/bid/103453
- https://access.redhat.com/errata/RHSA-2018:2927
- https://www.bouncycastle.org/releasenotes.html
- https://www.kb.cert.org/vuls/id/306792
- https://www.oracle.com/security-alerts/cpuoct2020.html
Get alerted when CVE-2018-5382 or the next vulnerability affects your stack