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


Severity

Recommended
critical

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.44% (75th 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-JAVA171IBMDEMO-4559183
  • published26 Jul 2021
  • disclosed30 Mar 2015

Introduced: 30 Mar 2015

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

How to fix?

Upgrade RHEL:7 java-1.7.1-ibm-demo to version 1:1.7.1.3.0-1jpp.2.el7_1 or higher.
This issue was patched in RHSA-2015:1020.

NVD Description

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

The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the "Bar Mitzvah" issue.

References

CVSS Scores

version 3.1