CVE-2018-5382

Medium

Description

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.

SeverityMedium
CVSS4.4
Exploit probability—
ProductBouncycastle Bc-java
PublishedApr 16, 2018
First seenApr 16, 2018
Weakness typeCWE-327CWE-327

How to fix

Update
  • org.bouncycastle:bcprov-jdk15on1.50 or later

Affected products

ProductAffected versionsFixed in
bouncycastle bc-javav ≤ 1.49—
redhat satellite6.4—
redhat satellite_capsule6.4—
org.bouncycastle:bcprov-jdk15onMavenv < 1.501.50

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.