Key Exchange without Entity Authentication Affecting foreman-cli package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (18th 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 IDSNYK-RHEL7-FOREMANCLI-6852206
  • published15 May 2024
  • disclosed14 May 2024

Introduced: 14 May 2024

CVE-2024-4871  (opens in a new tab)
CWE-322  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 foreman-cli.

NVD Description

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

A vulnerability was found in Satellite. When running a remote execution job on a host, the host's SSH key is not being checked. When the key changes, the Satellite still connects it because it uses "-o StrictHostKeyChecking=no". This flaw can lead to a man-in-the-middle attack (MITM), denial of service, leaking of secrets the remote execution job contains, or other issues that may arise from the attacker's ability to forge an SSH key. This issue does not directly allow unauthorized remote execution on the Satellite, although it can leak secrets that may lead to it.

CVSS Scores

version 3.1