Skip to content

GHSA-w285-wf9q-5w69 CVE-2016-1000352

In Bouncy Castle JCE Provider the ECIES implementation allowed the use of ECB mode

High Maven
Severity
7.4 / 10
High · CVSS 3.0
Exploit chance (EPSS)
2.17%
Chance of exploitation in the next 30 days. Higher than 82.25% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-326 Inadequate Encryption Strength
Fix
Available
3 packages have a fixed version

Description

In the Bouncy Castle JCE Provider version 1.55 and earlier the ECIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider.

Affected versions

Maven

PackageVulnerableFixed in
org.bouncycastle:bcprov-jdk14
< 1.56
1.56
org.bouncycastle:bcprov-jdk15
< 1.56
1.56
org.bouncycastle:bcprov-jdk15on
< 1.56
1.56

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.bouncycastle:bcprov-jdk14 Maven → 1.56

maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk14</artifactId><version>1.56</version></dependency>
gradle
implementation("org.bouncycastle:bcprov-jdk14:1.56")

org.bouncycastle:bcprov-jdk15 Maven → 1.56

maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk15</artifactId><version>1.56</version></dependency>
gradle
implementation("org.bouncycastle:bcprov-jdk15:1.56")

org.bouncycastle:bcprov-jdk15on Maven → 1.56

maven
<dependency><groupId>org.bouncycastle</groupId><artifactId>bcprov-jdk15on</artifactId><version>1.56</version></dependency>
gradle
implementation("org.bouncycastle:bcprov-jdk15on:1.56")

Severity breakdown

CVSS 3.0 7.4

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-326: Inadequate Encryption Strength

The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.

How to prevent it
  • Architecture and Design: Use an encryption scheme that is currently considered to be strong by experts in the field.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-p93r-85wp-75v3
Bouncy Castle Has Covert Timing Channel Vulnerability
High Also affects org.bouncycastle:bcprov-jdk14
GHSA-c3fc-8qff-9hwx
Bouncy Castle has an LDAP injection
Medium Also affects org.bouncycastle:bcprov-jdk14
GHSA-574f-3g2m-x479
Bouncy Castle for Java GOST 28147 CTR mode reuses keystream after 255 blocks
High Also affects org.bouncycastle:bcprov-jdk14
GHSA-67mf-3cr5-8w23
Bouncy Castle for Java on All (API modules) allows Excessive Allocation
Medium Also affects org.bouncycastle:bcprov-jdk14
GHSA-m44j-cfrm-g8qc
Bouncy Castle crafted signature and public key can be used to trigger an infinite loop
High Also affects org.bouncycastle:bcprov-jdk14
GHSA-v435-xc8x-wvr9
Bouncy Castle affected by timing side-channel for RSA key exchange ("The Marvin Attack")
Medium Also affects org.bouncycastle:bcprov-jdk14
GHSA-8xfc-gm6g-vgpv
Bouncy Castle certificate parsing issues cause high CPU usage during parameter evaluation.
High Also affects org.bouncycastle:bcprov-jdk14
GHSA-4h8f-2wvx-gg5w
Bouncy Castle Java Cryptography API vulnerable to DNS poisoning
High Also affects org.bouncycastle:bcprov-jdk14
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor