Use of a Broken or Risky Cryptographic Algorithm Affecting jboss-ejb-client package, versions <0:1.0.30-1.Final_redhat_1.1.ep6.el7


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.21% (59th 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-JBOSSEJBCLIENT-3507277
  • published26 Mar 2023
  • disclosed10 Feb 2015

Introduced: 10 Feb 2015

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

How to fix?

Upgrade RHEL:7 jboss-ejb-client to version 0:1.0.30-1.Final_redhat_1.1.ep6.el7 or higher.
This issue was patched in RHSA-2015:0848.

NVD Description

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

Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key or message data, which makes it easier for remote attackers to recover the plaintext form of a symmetric key via a series of crafted messages. NOTE: this vulnerability exists because of an incomplete fix for CVE-2011-2487.

CVSS Scores

version 3.1