LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000346: In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully valid...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a cryptographic validation flaw in Bouncy Castle JCE Provider 1.55 and earlier. If an application uses static Diffie-Hellman, a malicious peer key may expose information about the private key. Business risk depends on whether vulnerable Bouncy Castle code is embedded and whether static DH is actually used.

Executive priority

Treat as a targeted cryptographic exposure review, not a blanket emergency. Prioritize internet-facing or partner-facing systems using Java cryptography, especially where static Diffie-Hellman is configured. Patch through normal security update channels unless local exposure confirms static DH with vulnerable versions.

Technical view

The provider did not fully validate the other party's Diffie-Hellman public key. In static DH use, invalid keys can reveal private-key details. Bouncy Castle release 1.56 added key-parameter checks during agreement calculation. Downstream vendors issued security updates for affected packages and products.

Likely exposure

Exposure is most likely in Java applications, OS packages, or vendor products bundling Bouncy Castle JCE Provider 1.55 or earlier. The highest-risk case is static Diffie-Hellman key agreement. The provided CVE data does not list complete CPEs or a CVSS score.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The flaw is cryptographic and preconditioned on vulnerable Bouncy Castle versions plus static DH usage. Public advisories confirm vendor remediation but not exploitation in the wild.

Researcher notes

Evidence is strong for the vulnerable condition and fix, but incomplete for scoring and affected-product enumeration. The key question is whether a reachable protocol path uses static DH through Bouncy Castle 1.55 or earlier. Avoid assuming all Bouncy Castle consumers are exploitable.

Mitigation direction

  • Upgrade Bouncy Castle JCE Provider to release 1.56 or later.
  • Apply relevant Debian, Red Hat, Ubuntu, Oracle, or NetApp vendor updates.
  • Identify and update embedded bc-java or bcprov dependencies in applications.
  • For third-party products, follow the vendor advisory rather than replacing libraries manually.

Validation and detection

  • Inventory Java applications and products using Bouncy Castle JCE Provider.
  • Check dependency manifests, packaged JARs, and vendor package versions for 1.55 or earlier.
  • Determine whether static Diffie-Hellman key agreement is used.
  • Confirm patched systems include release 1.56 or vendor-fixed packages.
  • Document any appliances or bundled software awaiting vendor guidance.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-1000346 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.