CVE-2016-1000346

What it is

In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated. This can cause issues as invalid keys can be used to reveal details about the other party's private key where static Diffie-Hellman is in use. As of release 1.56 the key parameters are checked on agreement calculation.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.2% 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-06-04 21:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:38 UTC Last updatedMost recent change to the record

Why it ranks here

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

Details

Published

2018-06-04 21:29 UTC

Last modified

2026-06-17 00:38 UTC

Exploit probability

2.2% · EPSS, next 30 days

Weakness

CWE-320

Record status

Modified

Affected

• Bouncycastle bc-java ≤ 1.55
• Debian Linux 8.0

Attack profile CVSS 3.0 · 3.7

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

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-2016-1000346.md and follow it. Check whether this project is affected by CVE-2016-1000346. 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