CVE-2018-5382

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-04-16 14:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:00 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 4.4 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-04-16 14:29 UTC

Last modified

2026-06-17 02:00 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-327 · Broken cryptographic algorithm

Record status

Modified

Affected

• Bouncycastle bc-java ≤ 1.49
• Redhat Satellite 6.4
• Redhat Satellite Capsule 6.4

Attack profile CVSS 3.1 · 4.4

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2018-5382.md and follow it. Check whether this project is affected by CVE-2018-5382. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge