Skip to content
Noroxi
CVE-2016-1000346· NVD / CVE Program· CNA mitre

In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated.

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.

LowCVSS 3.7 · v3.0—No exploit Fix available
Published
Jun 4, 2018
Updated
Jun 16, 2026
EPSS
2.2% · 82th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

15

Monitor

Low priority for now.

CVSS
14 / 40 · 3.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.2%

Affected systems

VendorProduct
bouncycastlebc-java
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bouncycastle bc-javaup to 1.55 inclusive
  • debian debian linux8.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12bouncycastlebefore 1.56-11.56-1
Debian:8bouncycastlebefore 1.49+dfsg-3+deb8u31.49+dfsg-3+deb8u3
Mavenorg.bouncycastle:bcprov-jdk14before 1.561.56
Mavenorg.bouncycastle:bcprov-jdk15before 1.561.56
Mavenorg.bouncycastle:bcprov-jdk15onbefore 1.561.56
openSUSE:Tumbleweedbouncycastlebefore 1.68-3.21.68-3.2
Red Hat:satellite_capsule:6.4::el7ansiblerole-insights-clientbefore 0:1.5-1.el7sat0:1.5-1.el7sat
Red Hat:satellite_capsule:6.4::el7createrepo_cbefore 0:0.7.4-1.el7sat0:0.7.4-1.el7sat
Red Hat:satellite_capsule:6.4::el7createrepo_c-debuginfobefore 0:0.7.4-1.el7sat0:0.7.4-1.el7sat
Red Hat:satellite_capsule:6.4::el7createrepo_c-libsbefore 0:0.7.4-1.el7sat0:0.7.4-1.el7sat
Red Hat:satellite_capsule:6.4::el7foremanbefore 0:1.18.0.37-1.el7sat0:1.18.0.37-1.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-bootloaders-redhatbefore 0:201801241201-3.el7sat0:201801241201-3.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-bootloaders-redhat-tftpbootbefore 0:201801241201-3.el7sat0:201801241201-3.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-debugbefore 0:1.18.0.37-1.el7sat0:1.18.0.37-1.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-installerbefore 1:1.18.0.2-1.el7sat1:1.18.0.2-1.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-installer-katellobefore 0:3.7.0.10-1.el7sat0:3.7.0.10-1.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-proxybefore 0:1.18.0.1-1.el7sat0:1.18.0.1-1.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-proxy-contentbefore 0:3.7.0-8.el7sat0:3.7.0-8.el7sat
Red Hat:satellite_capsule:6.4::el7foreman-selinuxbefore 0:1.18.0.1-1.el7sat0:1.18.0.1-1.el7sat
Red Hat:satellite_capsule:6.4::el7goferbefore 0:2.12.1-1.el7sat0:2.12.1-1.el7sat
Red Hat:satellite_capsule:6.4::el7hfsplus-toolsbefore 0:332.14-12.el70:332.14-12.el7
Red Hat:satellite_capsule:6.4::el7hfsplus-tools-debuginfobefore 0:332.14-12.el70:332.14-12.el7
Red Hat:satellite_capsule:6.4::el7katellobefore 0:3.7.0-8.el7sat0:3.7.0-8.el7sat
Red Hat:satellite_capsule:6.4::el7katello-certs-toolsbefore 0:2.4.0-2.el7sat0:2.4.0-2.el7sat

+96

Other highest-scoring records for the same primary product.

  • CVE-2007-6721The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impac
    41Plan
  • CVE-2018-1000613Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of
    40Plan
  • CVE-2026-58062Stapled OCSP response accepted without binding to the checked certificate
    37Monitor
  • CVE-2026-8763Name Constraints bypass via trailing dot in rfc822Name and URI
    37Monitor
  • CVE-2026-59650MTI/A0 DH agreement exponentiates unvalidated peer value
    37Monitor
  • CVE-2026-59638JSSE hostname verifier CN-fallback enabled by default despite documented opt-in
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:bouncycastle1.56-1 · Debian:12Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk141.56Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk151.56Package registry (OSV)
Maven:org.bouncycastle:bcprov-jdk15on1.56Package registry (OSV)
opensuse:bouncycastle1.68-3.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:ansiblerole-insights-client0:1.5-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:createrepo_c0:0.7.4-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:createrepo_c-debuginfo0:0.7.4-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:createrepo_c-libs0:0.7.4-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman0:1.18.0.37-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman-bootloaders-redhat0:201801241201-3.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman-bootloaders-redhat-tftpboot0:201801241201-3.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman-debug0:1.18.0.37-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman-installer1:1.18.0.2-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman-installer-katello0:3.7.0.10-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:foreman-proxy0:1.18.0.1-1.el7sat · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)
red hat:SOAPpy0:0.11.6-17.el7 · Red Hat:satellite_capsule:6.4::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records