CVE-2018-5382

MEDIUMNVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.4Exploit: NoneExposed: 0

A fix is available — apply it.

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 v3
4.4
EG Score
4.4(medium)
EPSS
17.6%
KEV
Not listed

Published

April 16, 2018

Last Modified

May 12, 2025

References (10)

Vendor Advisories for CVE-2018-5382(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatyaml-cpp-0:0.5.1-7.el7sat2018-10-16redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.bouncycastle:bcprov-jdk15on1.46, 1.47, 1.48, 1.491.50—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-09 19:06 UTCEPSS rescore
  2. 2026-07-08 15:11 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-07 13:42 UTCEPSS rescore
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 02:20 UTCEPSS rescore
  9. 2026-07-05 02:27 UTCEPSS rescore
  10. 2026-07-04 10:26 UTCOSV refresh
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-01 15:03 UTCEPSS rescore
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-06-30 23:20 UTCEPSS rescore
  16. 2026-06-30 23:20 UTCEPSS rescore
  17. 2026-06-29 14:03 UTCEPSS rescore
  18. 2026-06-28 14:04 UTCEPSS rescore
  19. 2026-06-28 04:53 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-27 03:06 UTCEPSS rescore
  22. 2026-06-27 03:06 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 53 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-23 21:30 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-22 14:23 UTCEPSS rescore
  5. 2026-06-22 14:23 UTCEPSS rescore
  6. 2026-06-21 14:54 UTCEPSS rescore
  7. 2026-06-21 14:54 UTCEPSS rescore
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-19 19:23 UTCEPSS rescore
  11. 2026-06-19 19:23 UTCEPSS rescore
  12. 2026-06-18 17:50 UTCEPSS rescore
  13. 2026-06-18 17:50 UTCEPSS rescore
  14. 2026-06-17 17:50 UTCEPSS rescore
  15. 2026-06-16 17:50 UTCEPSS rescore
  16. 2026-06-16 17:50 UTCEPSS rescore
  17. 2026-06-15 21:43 UTCOSV refresh
  18. 2026-06-15 17:45 UTCEPSS rescore
  19. 2026-06-14 23:15 UTCEPSS rescore
  20. 2026-06-14 23:15 UTCEPSS rescore
  21. 2026-06-13 22:58 UTCEPSS rescore
  22. 2026-06-12 23:09 UTCEPSS rescore
  23. 2026-06-12 23:09 UTCEPSS rescore
  24. 2026-06-11 13:57 UTCEPSS rescore
  25. 2026-06-10 22:16 UTCEPSS rescore
  26. 2026-06-10 13:19 UTCEPSS rescore
  27. 2026-06-08 14:14 UTCEPSS rescore
  28. 2026-06-07 15:22 UTCEPSS rescore
  29. 2026-06-07 15:22 UTCEPSS rescore
  30. 2026-06-06 13:45 UTCEPSS rescore
  31. 2026-06-06 13:45 UTCEPSS rescore
  32. 2026-06-05 22:45 UTCEPSS rescore
  33. 2026-06-05 22:45 UTCEPSS rescore
  34. 2026-06-05 06:08 UTCEPSS rescore
  35. 2026-06-05 06:08 UTCEPSS rescore
  36. 2026-06-04 13:10 UTCEPSS rescore
  37. 2026-06-04 13:10 UTCEPSS rescore
  38. 2026-06-02 20:11 UTCEPSS rescore
  39. 2026-06-01 13:50 UTCEPSS rescore
  40. 2026-05-31 22:29 UTCEPSS rescore
  41. 2026-05-31 22:29 UTCEPSS rescore
  42. 2026-05-31 00:14 UTCEPSS rescore
  43. 2026-05-31 00:14 UTCEPSS rescore
  44. 2026-05-29 13:41 UTCEPSS rescore
  45. 2026-05-28 13:43 UTCEPSS rescore
  46. 2026-05-28 13:42 UTCEPSS rescore
  47. 2026-05-28 09:13 UTCEG score recompute
  48. 2026-05-28 09:13 UTCVendor advisory
  49. 2026-05-27 13:38 UTCEPSS rescore
  50. 2026-05-26 13:42 UTCEPSS rescore
  51. 2026-05-26 13:42 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore

Frequently asked(5)

What is CVE-2018-5382?
CVE-2018-5382 is a medium vulnerability published on April 16, 2018. 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.…
When was CVE-2018-5382 disclosed?
CVE-2018-5382 was first published in the National Vulnerability Database on April 16, 2018, with the most recent update on May 12, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-5382 actively exploited?
CVE-2018-5382 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-5382?
CVE-2018-5382 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2018-5382?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-5382, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-5382

Explore →

Is Your Infrastructure Affected by CVE-2018-5382?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs