Bouncy Castle JCE Provider up to 1.55 DHIES/ECIES 7pk time and state

Summaryinfo

A vulnerability has been found in Bouncy Castle JCE Provider up to 1.55 and classified as critical. This affects an unknown part of the component DHIES/ECIES. The manipulation leads to 7pk time and state. This vulnerability is referenced as CVE-2016-1000345. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Bouncy Castle JCE Provider up to 1.55. It has been rated as critical. This issue affects an unknown part of the component DHIES/ECIES. The manipulation with an unknown input leads to a 7pk time and state vulnerability. Using CWE to declare the problem leads to CWE-361. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES/ECIES CBC mode vulnerable to padding oracle attack. For BC 1.55 and older, in an environment where timings can be easily observed, it is possible with enough observations to identify when the decryption is failing due to padding.

The bug was discovered 07/07/2018. The weakness was published 06/04/2018 (GitHub Repository). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2016-1000345 since 06/04/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

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-0562). Similar entries are available at VDB-118491, VDB-118820, VDB-118821 and VDB-118822. Statistical analysis made it clear that VulDB provides the best quality 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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion