WaratekVRT Sign in

CVE-2018-5382

Affected software3 products, listed below
Severity4.4 Medium CVSS 3.1 2 scores
Fixed in1.50
WeaknessCWE-327
Published16 Apr 2018
Updated17 Jun 2026

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.

CWE-354

Exploitation status

No public exploit

No exploit has been reported in the sources we check. Published 8 years ago.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS 0.26% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

CVSS

4.4 MEDIUM v3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

VersionScoreBandVectorAssignerType
CVSS 3.1 4.4 MEDIUM CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N NVD Primary published
CVSS 2.0 3.6 none AV:L/AC:L/Au:N/C:P/I:P/A:N NVD Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.bouncycastle:bcprov-jdk15on 0 1.50 unbounded

Products and versions

4 products, 4 version entries
SourceVendorProductSchemeAffected versions
nvd bouncycastle bc-java generic ≤ 1.49
osv org.bouncycastle bcprov-jdk15on generic < 1.50
nvd redhat satellite generic 6.4
nvd redhat satellite capsule generic 6.4

References

URLTags
https://access.redhat.com/errata/RHSA-2018:2927 WEB
https://www.bouncycastle.org/releasenotes.html WEB
https://www.kb.cert.org/vuls/id/306792 WEB
https://www.oracle.com/security-alerts/cpuoct2020.html WEB
http://www.securityfocus.com/bid/103453 WEB

Timeline

Published2018-04-16By the CVE Program.
NVD record modified2026-06-17NVD's own last-modified date for this record.