LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000343: In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak priv...

In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if used with default values. If the JCA key pair generator is not explicitly initialised with DSA parameters, 1.55 and earlier generates a private value assuming a 1024 bit key size. In earlier releases this can be dealt with by explicitly passing parameters to the key pair generator.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue can cause applications to create weaker DSA private keys when using affected Bouncy Castle defaults. Business impact depends on whether those generated keys protect signatures, authentication, or trust decisions. Systems only bundling the library but not generating DSA keys this way may have limited exposure.

Executive priority

Treat as a targeted cryptographic hygiene issue, not a broad emergency from the provided evidence. Prioritize systems that generate or rely on long-lived DSA keys for trust decisions.

Technical view

Bouncy Castle JCE Provider version 1.55 and earlier generated a weak DSA private value when the JCA key pair generator was not explicitly initialized with DSA parameters. The CVE states earlier releases can avoid the issue by explicitly passing parameters to the generator.

Likely exposure

Exposure is most likely in Java applications or vendor products using Bouncy Castle JCE Provider 1.55 or earlier to generate DSA key pairs with default, uninitialized parameters.

Exploitation context

The source bundle does not show KEV listing or active exploitation. Exploitability depends on whether vulnerable code generated DSA keys and whether those keys are security-relevant. The bundle provides no public exploit evidence or CVSS score.

Researcher notes

Key evidence is the CVE description and vendor advisories. Affected-package details vary by distribution or product. The bundle does not provide CVSS, CWE, confirmed exploitation, or a complete universal fixed-version statement.

Mitigation direction

  • Upgrade Bouncy Castle through the relevant vendor or distribution advisory path.
  • For older retained versions, explicitly pass DSA parameters to the key pair generator.
  • Identify security-sensitive DSA keys generated by affected code paths.
  • Evaluate replacement of impacted generated keys with application and cryptography owners.
  • Track package-specific guidance from Debian, Red Hat, Ubuntu, Oracle, and NetApp.

Validation and detection

  • Inventory applications and products containing Bouncy Castle JCE Provider 1.55 or earlier.
  • Search code for DSA key pair generation using Bouncy Castle defaults.
  • Confirm whether generators are explicitly initialized with DSA parameters.
  • Map generated DSA keys to signing, authentication, or trust workflows.
  • Review vendor advisories for fixed package versions in managed platforms.
Prepared
Confidence
medium
Sources
7

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-1000343 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
9Source 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.