Improper Validation of Integrity Check Value Affecting bouncycastle package, versions <1.48+dfsg-2


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.07% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-BOUNCYCASTLE-278560
  • published16 Apr 2018
  • disclosed16 Apr 2018

Introduced: 16 Apr 2018

CVE-2018-5382  (opens in a new tab)
CWE-354  (opens in a new tab)

How to fix?

Upgrade Debian:unstable bouncycastle to version 1.48+dfsg-2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream bouncycastle package and not the bouncycastle package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Scores

version 3.1