Vulnerabilities · 2018 · Bouncycastle
CVE-2018-5382
Bouncycastle Bc-java vulnerability
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.
Affected products
Bc-java, Satellite, Satellite Capsule. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Bouncycastle Bc-java runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- www.bouncycastle.org/releasenotes.html · Vendor Advisory
- www.securityfocus.com/bid/103453 · Third Party Advisory
- access.redhat.com/errata/RHSA-2018:2927 · Third Party Advisory
- www.kb.cert.org/vuls/id/306792 · Third Party Advisory
- www.oracle.com/security-alerts/cpuoct2020.html · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2018-5382
- cve.org/CVERecord?id=CVE-2018-5382
More vulnerabilities in Bouncycastle products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.