CVE-2018-5382

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.
References
Link Resource
https://www.kb.cert.org/vuls/id/306792 Third Party Advisory US Government Resource
https://www.bouncycastle.org/releasenotes.html Release Notes Vendor Advisory
http://www.securityfocus.com/bid/103453 Third Party Advisory VDB Entry
https://access.redhat.com/errata/RHSA-2018:2927 Third Party Advisory
https://www.oracle.com/security-alerts/cpuoct2020.html Third Party Advisory
Configurations

Configuration 1

cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api:*:*:*:*:*:*:*:*
cpe:2.3:a:redhat:satellite:6.4:*:*:*:*:*:*:*
cpe:2.3:a:redhat:satellite_capsule:6.4:*:*:*:*:*:*:*

Information

Published : 2018-04-16 02:29

Updated : 2022-04-20 03:31


NVD link : CVE-2018-5382

Mitre link : CVE-2018-5382

Products Affected
No products.
CWE