You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bouncy Castle is vulnerable to hash collision attacks. The library keystore files uses a HMAC hash that is only 16 bits long, allowing a malicious user to retrieve the password used for keystore integrity verification checks. This vulnerability only affects users of the BKS-V1 keystore format, which was re-introduced since 1.49. Since it is re-introduced in Bouncy Castle 1.49, users of Bouncy Castle 1.49 and above may be affected if the legacy BKS-V1 is being used.
This is an updated response as MITRE have now fixed the wording of the CVE to reflect what it is actually about, which is BKS, not BKS-V1 (BKS-V1 did not exist as a keystore type prior to 1.49) Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5382
We are hoping the new wording will clear this up for the tool vendors.
Bouncy Castle is vulnerable to hash collision attacks. The library keystore files uses a HMAC hash that is only 16 bits long, allowing a malicious user to retrieve the password used for keystore integrity verification checks. This vulnerability only affects users of the
BKS-V1
keystore format, which was re-introduced since 1.49. Since it is re-introduced in Bouncy Castle 1.49, users of Bouncy Castle 1.49 and above may be affected if the legacy BKS-V1 is being used.https://sca.analysiscenter.veracode.com/vulnerability-database/security/hash-collision/java/sid-27749
The text was updated successfully, but these errors were encountered: