How severe is CVE-2016-1000346?

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

Is CVE-2016-1000346 being actively exploited?

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

What products are affected by CVE-2016-1000346?

CVE-2016-1000346 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-1000346?

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

When was CVE-2016-1000346 published?

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

CVE-2016-1000346

CVE-2016-1000346 is a low-severity vulnerability in Bouncycastle Bc-java with a CVSS 3.x base score of 3.7. 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-320.

Key facts

Severity: Low (CVSS 3.x base score 3.7)
CVSS v2: 4.3
EPSS exploit prediction: 2% (81st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-320
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 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.

Frequently asked questions

What is CVE-2016-1000346?: 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.
How severe is CVE-2016-1000346?: CVE-2016-1000346 has a CVSS 3.x base score of 3.7, rated low severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2016-1000346 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-1000346?: CVE-2016-1000346 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-1000346?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-1000346 published?: CVE-2016-1000346 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-320 vulnerabilities

CVE-2016-10467 — Critical (CVSS 9.8): In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile and Snapdragon Mobile SD…
CVE-2016-10421 — Critical (CVSS 9.8): In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear MDM9206,…
CVE-2018-0124 — Critical (CVSS 9.8): A vulnerability in Cisco Unified Communications Domain Manager could allow an unauthenticated, remote attacker to…
CVE-2015-0936 — Critical (CVSS 9.8): Ceragon FibeAir IP-10 have a default SSH public key in the authorized_keys file for the mateidu user, which allows…
CVE-2015-4166 — Critical (CVSS 9.8): Cloudera Key Trustee Server before 5.4.3 does not store keys synchronously, which might allow attackers to have…
CVE-2024-36391 — Critical (CVSS 9.1): MileSight DeviceHub - CWE-320: Key Management Errors may allow Authentication Bypass and Man-In-The-Middle Traffic

Browse all CWE-320 vulnerabilities →