Skip to content

In Bouncy Castle JCE Provider the DSA key pair generator generates a weak private key if used with default values

High severity GitHub Reviewed Published Oct 17, 2018 to the GitHub Advisory Database • Updated Sep 12, 2025

Package

maven org.bouncycastle:bcprov-jdk14 (Maven)

Affected versions

< 1.56

Patched versions

1.56
maven org.bouncycastle:bcprov-jdk15 (Maven)
< 1.56
1.56
maven org.bouncycastle:bcprov-jdk15on (Maven)
< 1.56
1.56

Description

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.

References

Published by the National Vulnerability Database Jun 4, 2018
Published to the GitHub Advisory Database Oct 17, 2018
Reviewed Jun 16, 2020
Last updated Sep 12, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(81st percentile)

Weaknesses

No CWEs

CVE ID

CVE-2016-1000343

GHSA ID

GHSA-rrvx-pwf8-p59p

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.