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


Severity

Recommended
critical

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

Exploit Maturity
Mature
EPSS
0.53% (78th 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-5164673
  • published26 Jul 2021
  • disclosed24 Aug 2016

Introduced: 24 Aug 2016

CVE-2016-2183  (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.4.1-1jpp.2.el7 or higher.
This issue was patched in RHSA-2017:0336.

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 DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a "Sweet32" attack.

References

CVSS Scores

version 3.1