Use of a Broken or Risky Cryptographic Algorithm Affecting java-1.8.0-ibm-jdbc package, versions <1:1.8.0.7.5-1.el8_5


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.25% (66th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-JAVA180IBMJDBC-1932041
  • published20 Oct 2021
  • disclosed19 Oct 2021

Introduced: 19 Oct 2021

CVE-2021-35550  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:8 java-1.8.0-ibm-jdbc to version 1:1.8.0.7.5-1.el8_5 or higher.
This issue was patched in RHSA-2022:0970.

NVD Description

Note: Versions mentioned in the description apply only to the upstream java-1.8.0-ibm-jdbc package and not the java-1.8.0-ibm-jdbc package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

Vulnerability in the Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Java SE: 7u311, 8u301, 11.0.12; Oracle GraalVM Enterprise Edition: 20.3.3 and 21.2.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via TLS to compromise Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Java SE, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.1 Base Score 5.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

References

CVSS Scores

version 3.1