CVE-2018-5382
16.04.2018, 14:29
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.Enginsight
Vendor | Product | Version |
---|---|---|
bouncycastle | bc-java | 𝑥 ≤ 1.49 |
redhat | satellite | 6.4 |
redhat | satellite_capsule | 6.4 |
𝑥
= Vulnerable software versions

Debian Releases
Common Weakness Enumeration
- CWE-327 - Use of a Broken or Risky Cryptographic AlgorithmThe use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information.
- CWE-354 - Improper Validation of Integrity Check ValueThe software does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
References