Homepage

Use of a Broken or Risky Cryptographic Algorithm Affecting java-1.7.1-ibm-jdbc package, versions <1:1.7.1.3.10-1jpp.1.el7_1

Severity

 Recommended
critical

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
97.36% (100th 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-RHEL7-JAVA171IBMJDBC-5083514
  • published26 Jul 2021
  • disclosed20 May 2015
Report a new vulnerability Found a mistake?

Introduced: 20 May 2015

CVE-2015-4000  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:7 java-1.7.1-ibm-jdbc to version 1:1.7.1.3.10-1jpp.1.el7_1 or higher.
This issue was patched in RHSA-2015:1485.

NVD Description

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

The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not properly convey a DHE_EXPORT choice, which allows man-in-the-middle attackers to conduct cipher-downgrade attacks by rewriting a ClientHello with DHE replaced by DHE_EXPORT and then rewriting a ServerHello with DHE_EXPORT replaced by DHE, aka the "Logjam" issue.

References