Menu

Star on GitHub · 3.2k

CVE-2016-1000346

3.7 · LOW

In the Bouncy Castle JCE Provider version 1.55 and earlier the other party DH public key is not fully validated.

Published Jun 4, 2018CWE-320EPSS 2.17%

Overview

CVE-2016-1000346 is a low-severity vulnerability. It was published on June 4, 2018 and has a CVSS 3.0 base score of 3.7 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.7, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-1000346?

CVE-2016-1000346 is a low-severity vulnerability. It was published on June 4, 2018 and has a CVSS 3.0 base score of 3.7 (LOW).

How severe is CVE-2016-1000346?

This vulnerability has a CVSS 3.0 base score of 3.7, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-1000346?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-1000346?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-1000346 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2016

View all