CVE-2018-5382
Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions
- State
- Published
- Severity
- Not scored
- Published
- Apr 16, 2018
- Updated
- Sep 16, 2024
- Reserved
- Jan 12, 2018
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.
Scores
The record has no CVSS score.
Weaknesses
- CWE-327 Use of a Broken or Risky Cryptographic Algorithm
Affected Products
| Product | Versions |
|---|---|
Bouncy CastleLegion of the Bouncy Castle |
|
References
- 103453vdb-entry
- RHSA-2018:2927vendor-advisory
- VU#306792third-party-advisory
- https://www.bouncycastle.org/releasenotes.html
- https://www.oracle.com/security-alerts/cpuoct2020.html
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.