How severe is CVE-2016-1000341?

CVE-2016-1000341 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2016-1000341 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-1000341?

CVE-2016-1000341 primarily affects Bouncycastle Bc-java. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-1000341?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2016-1000341 published?

CVE-2016-1000341 was published on 2018-06-04 and last updated on 2026-06-17.

CVE-2016-1000341

CVE-2016-1000341 is a medium-severity vulnerability in Bouncycastle Bc-java with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-361.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v2: 4.3
EPSS exploit prediction: 3% (83rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-361
Affected product: Bouncycastle Bc-java
Published: 2018-06-04
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2016-1000341?: 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.
How severe is CVE-2016-1000341?: CVE-2016-1000341 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2016-1000341 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (83rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-1000341?: CVE-2016-1000341 primarily affects Bouncycastle Bc-java. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-1000341?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-1000341 published?: CVE-2016-1000341 was published on 2018-06-04 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:bouncycastle:bc-java:*:*:*:*:*:*:*:*
cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*

More vulnerabilities in Bouncycastle Bc-java

CVE-2007-6721 — Critical (CVSS 10.0): The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before…
CVE-2018-1000613 — Critical (CVSS 9.8): Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60…
CVE-2020-28052 — High (CVSS 8.1): An issue was discovered in Legion of the Bouncy Castle BC Java 1.65 and 1.66. The OpenBSDBCrypt.checkPassword utility…
CVE-2019-17359 — High (CVSS 7.5): The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and…
CVE-2018-1000180 — High (CVSS 7.5): Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key…
CVE-2016-1000343 — High (CVSS 7.5): In the Bouncy Castle JCE Provider version 1.55 and earlier the DSA key pair generator generates a weak private key if…

All CVEs affecting Bouncycastle Bc-java →

Other CWE-361 vulnerabilities

CVE-2016-7547 — Critical (CVSS 9.8): A command execution flaw on the Trend Micro Threat Discovery Appliance 2.6.1062r1 exists with the timezone parameter in…
CVE-2016-7036 — Critical (CVSS 9.8): python-jose before 1.3.2 allows attackers to have unspecified impact by leveraging failure to use a constant time…
CVE-2016-1643 — High (CVSS 8.8): The ImageInputType::ensurePrimaryContent function in WebKit/Source/core/html/forms/ImageInputType.cpp in Blink, as used…
CVE-2015-5300 — High (CVSS 7.5): The panic_gate check in NTP before 4.2.8p5 is only re-enabled after the first change to the system clock that was…
CVE-2016-7037 — High (CVSS 7.5): The verify function in Encryption/Symmetric.php in Malcolm Fell jwt before 1.0.3 does not use a timing-safe function…
CVE-2016-1000345 — Medium (CVSS 5.9): In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle…

Browse all CWE-361 vulnerabilities →