Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hash Collision issue with bcprov-jdk15on-1.68 ,bcprov-ext-jdk15on-1.68 & bctls-jdk15on-1.68 #900

Closed
sumitblore opened this issue Mar 10, 2021 · 1 comment

Comments

@sumitblore
Copy link

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

@dghgit
Copy link
Contributor

dghgit commented Mar 10, 2021

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.

@dghgit dghgit closed this as completed Mar 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants