Bouncy Castle BKS-V1 keystore files vulnerable to trivial hash collisions (Legion of the Bouncy Castle Bouncy Castle)

CVE-2018-5382
MEDIUM 4.4

At a glance

Source
NVD
EPSS
EPSS 0.26 % · percentile 18 ()
State
PUBLISHED
Published
Updated
Assigner
certcc
NVD status
Modified

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.

Weaknesses (CWE)

  • CWE-327 — Use of a Broken or Risky Cryptographic Algorithm
  • CWE-354 — Improper Validation of Integrity Check Value

References

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 4.4CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NNVD · nvd@nist.gov (Primary)
CVSS 2.0LOW 3.6AV:L/AC:L/Au:N/C:P/I:P/A:NNVD · nvd@nist.gov (Primary)

Advisories

European references

CERT-FR advisories

Affected configurations (NVD CPE)

Affected products

ProductVersions
Legion of the Bouncy Castle · Bouncy Castleaffected all < 1.47

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD