Use of a Broken or Risky Cryptographic Algorithm Affecting podman-docker package, versions <3:4.4.1-10.1.rhaos4.14.el8


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.11% (46th 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-RHEL8-PODMANDOCKER-6838928
  • published13 May 2024
  • disclosed5 Jul 2023

Introduced: 5 Jul 2023

CVE-2023-3089  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade RHEL:8 podman-docker to version 3:4.4.1-10.1.rhaos4.14.el8 or higher.
This issue was patched in RHSA-2023:5009.

NVD Description

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

A compliance problem was found in the Red Hat OpenShift Container Platform. Red Hat discovered that, when FIPS mode was enabled, not all of the cryptographic modules in use were FIPS-validated.

CVSS Scores

version 3.1