CVE-2018-5382

CVSS v3.1 4.4 (Medium)
44% Progress
CVSS v2.0 3.6 (Low)
36% Progress
EPSS 0.07 % (31th)
0.07% Progress
Affected Products 3
Advisories 2

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.

Weaknesses
CWE-327
Use of a Broken or Risky Cryptographic Algorithm
CWE-354
Improper Validation of Integrity Check Value
CVE Status
PUBLISHED
CNA
CERT/CC
Published Date
2018-04-16 14:29:01
(6 years ago)
Updated Date
2022-04-20 15:31:06
(2 years ago)

Affected Products

Loading...
Loading...
Loading...

Configuration #1

    CPE23 From Up To
  Bouncycastle Legion-of-the-bouncy-castle-java-crytography-api 1.49 and prior versions cpe:2.3:a:bouncycastle:legion-of-the-bouncy-castle-java-crytography-api <= 1.49

Configuration #2

    CPE23 From Up To
  Redhat Satellite 6.4 cpe:2.3:a:redhat:satellite:6.4
  Redhat Satellite Capsule 6.4 cpe:2.3:a:redhat:satellite_capsule:6.4
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...