Bouncy Castle JCE Provider up to 1.55 DH Public Key key management

Summaryinfo

A vulnerability was found in Bouncy Castle JCE Provider up to 1.55 and classified as critical. This vulnerability affects unknown code of the component DH Public Key Handler. The manipulation results in key management. This vulnerability is identified as CVE-2016-1000346. The attack can be executed remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Bouncy Castle JCE Provider up to 1.55. Affected is an unknown code of the component DH Public Key Handler. The manipulation with an unknown input leads to a key management vulnerability. CWE is classifying the issue as CWE-320. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The bug was discovered 07/07/2018. The weakness was released 06/04/2018 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2016-1000346 since 06/04/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.001.

The vulnerability scanner Nessus provides a plugin with the ID 110948 (Debian DLA-1418-1 : bouncycastle security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 171315 (OpenSUSE Security Update for bouncycastle (openSUSE-SU-2018:1689-1)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (110948) and EUVD (EUVD-2018-0591). Entries connected to this vulnerability are available at VDB-118491, VDB-118820, VDB-118821 and VDB-118822. Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Bouncy Castle

Name

• JCE Provider

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.44
• 1.45
• 1.46
• 1.47
• 1.48
• 1.49
• 1.50
• 1.51
• 1.52
• 1.53
• 1.54
• 1.55

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion