CVE-2024-4871: Foreman: host ssh key not being checked in remote execution
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.
Other sources
When running a remote execution job on a host, the ssh key of the host is not being checked. When the key changes, the Satellite connects it anyway because it uses "-o StrictHostKeyChecking=no". This can lead to MITM, DoS, leaking of whatever secrets the remote execution job contains, or whatever other issues may arise from the attacker being able to forge a ssh key. This does not directly allow unauthorized remote execution on the Satellite (although it can leak secrets leading to it)..
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-4871?
CVE-2024-4871 is classified as a high severity vulnerability due to the potential for man-in-the-middle (MITM) attacks.
How do I fix CVE-2024-4871?
To mitigate CVE-2024-4871, ensure you configure SSH to verify host keys by disabling the '-o StrictHostKeyChecking=no' option.
What systems are affected by CVE-2024-4871?
CVE-2024-4871 affects Red Hat Satellite configured to run remote execution jobs.
What are the risks associated with CVE-2024-4871?
The primary risk of CVE-2024-4871 is that it allows an attacker to perform a man-in-the-middle attack when SSH keys are not verified.
When was CVE-2024-4871 disclosed?
CVE-2024-4871 was disclosed in 2024, detailing vulnerabilities in the Red Hat Satellite remote execution functionality.