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.
The product uses a broken or risky cryptographic algorithm or protocol.
The product 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.
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/103453 | third party advisory vdb entry |
| https://access.redhat.com/errata/RHSA-2018:2927 | third party advisory vendor advisory |
| https://www.kb.cert.org/vuls/id/306792 | third party advisory us government resource |
| https://www.bouncycastle.org/releasenotes.html | release notes vendor advisory |
| https://www.oracle.com/security-alerts/cpuoct2020.html | third party advisory |