Use of a Broken or Risky Cryptographic Algorithm Affecting rubygem-rake package, versions <0:0.9.2.2-41.el7sat


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.07% (34th 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-RUBYGEMRAKE-5379285
  • published27 Mar 2023
  • disclosed30 Mar 2012

Introduced: 30 Mar 2012

CVE-2018-5382  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:7 rubygem-rake to version 0:0.9.2.2-41.el7sat or higher.
This issue was patched in RHSA-2018:2927.

NVD Description

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

The default BKS keystore use an HMAC that is only 16 bits long, which can allow an attacker to compromise the integrity of a BKS keystore. Bouncy Castle release 1.47 changes the BKS format to a format which uses a 160 bit HMAC instead. This applies to any BKS keystore generated prior to BC 1.47. For situations where people need to create the files for legacy reasons a specific keystore type "BKS-V1" was introduced in 1.49. It should be noted that the use of "BKS-V1" is discouraged by the library authors and should only be used where it is otherwise safe to do so, as in where the use of a 16 bit checksum for the file integrity check is not going to cause a security issue in itself.

CVSS Scores

version 3.1