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.
Problem types
Key Exchange without Entity Authentication
Product status
0:4.3.14-1.el8sat (rpm) before *
0:3.9.1.8-1.el8sat (rpm) before *
1:3.9.3.2-1.el8sat (rpm) before *
0:2.16.9-1.el8pc (rpm) before *
0:3.39.15-1.el8pc (rpm) before *
0:1.8.3-1.el8sat (rpm) before *
0:13.0.6-1.el8sat (rpm) before *
0:12.0.7-1.el8sat (rpm) before *
0:4.11.0.15-1.el8sat (rpm) before *
0:3.0.0-1.el8sat (rpm) before *
0:0.10.6-1.el8sat (rpm) before *
0:6.15.2-1.el8sat (rpm) before *
Timeline
| 2024-05-02: | Reported to Red Hat. |
| 2024-05-14: | Made public. |
References
access.redhat.com/security/cve/CVE-2024-4871
bugzilla.redhat.com/show_bug.cgi?id=2278627 (RHBZ#2278627)
access.redhat.com/errata/RHBA-2024:4589 (RHBA-2024:4589)
access.redhat.com/security/cve/CVE-2024-4871
bugzilla.redhat.com/show_bug.cgi?id=2278627 (RHBZ#2278627)
