LiveActive security incident?Get immediate response
CVE Record

CVE-2016-1000341: In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing...

In the Bouncy Castle JCE Provider version 1.55 and earlier DSA signature generation is vulnerable to timing attack. Where timings can be closely observed for the generation of signatures, the lack of blinding in 1.55, or earlier, may allow an attacker to gain information about the signature's k value and ultimately the private value as well.

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

Security readout for executives and security teams

Plain-English summary

This flaw affects older Bouncy Castle Java cryptography code. If an attacker can closely measure DSA signature generation timing, they may learn enough about signing operations to recover the private key. That could undermine signatures made by affected applications.

Executive priority

Treat as a targeted cryptographic key exposure risk, not a broad wormable emergency. Prioritize externally reachable signing services, identity systems, and vendor products that embed old Bouncy Castle versions.

Technical view

Bouncy Castle JCE Provider 1.55 and earlier lacked blinding in DSA signature generation. Closely observed timing may leak information about the per-signature k value, which can ultimately expose the DSA private value. The sources do not provide CVSS, CWE, or confirmed exploitation evidence.

Likely exposure

Exposure is most likely in Java applications, products, or appliances bundling Bouncy Castle JCE Provider 1.55 or earlier and performing DSA signing. Embedded copies inside vendor products may be harder to identify.

Exploitation context

The CVE requires closely observable signature-generation timing. KEV is false in the provided bundle, and no cited source confirms active exploitation. Risk rises where attackers can repeatedly interact with a DSA signing service and measure timing precisely.

Researcher notes

Focus validation on actual DSA signing use, not merely library presence. The vulnerable condition is timing leakage during signature generation without blinding. Evidence in the bundle does not establish public exploit use or a universal product list.

Mitigation direction

  • Inventory Java services and products using Bouncy Castle JCE Provider.
  • Upgrade Bouncy Castle beyond version 1.55 through supported vendor packages.
  • Apply relevant Debian, Red Hat, Ubuntu, Oracle, or NetApp security updates.
  • Prioritize systems that generate DSA signatures for external or shared users.
  • For embedded copies, request vendor guidance if update status is unclear.

Validation and detection

  • Confirm no runtime classpath loads Bouncy Castle JCE Provider 1.55 or earlier.
  • Check packaged applications for embedded bcprov artifacts.
  • Identify whether affected systems perform DSA signature generation.
  • Verify applicable vendor advisories are installed on managed platforms.
  • Document remaining exceptions and compensating vendor guidance.
Prepared
Confidence
high
Sources
9

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-1000341 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.