Back

MEDIUM

Foreman: host ssh key not being checked in remote execution

Published May 14, 2024

Description

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.

Affected products

Remediation

Vendor solution

Currently there is no mitigation available for this vulnerability. Please perform the necessary updates as they become available.

Red Hat statement

Red Hat rates this as a Moderate impact. Even though an attacker may access, they may need a functional SSH key with enough access to jeopardize the environment.

Red Hat mitigation

Currently there is no mitigation available for this vulnerability. Please perform the necessary updates as they become available.

Weaknesses (1)

References (5)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner redhat
Published May 14, 2024
Updated Feb 25, 2026
Reserved May 14, 2024
CISA Vulnrichment
Updated May 14, 2024
NVD
Status Deferred
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date May 14, 2024