Remote-job interception via disabled SSH host-key verification
Published May 14, 2024 · Updated Feb 25, 2026
SSH host-key verification failure in Foreman 3.9.1.8 and Red Hat Satellite allows man-in-the-middle attackers to intercept jobs. The smart-proxy SSH runner starts connections with StrictHostKeyChecking=no, so a changed host key is accepted instead of terminating the connection. The attacker must hold a network position and possess a functional SSH key with sufficient access; exposure is limited to job secrets and commands, not direct execution on Satellite.
Summary
What happened
SSH host-key verification failure in Foreman 3.9.1.8 and Red Hat Satellite allows man-in-the-middle attackers to intercept jobs. The smart-proxy SSH runner starts connections with StrictHostKeyChecking=no, so a changed host key is accepted instead of terminating the connection. The attacker must hold a network position and possess a functional SSH key with sufficient access; exposure is limited to job secrets and commands, not direct execution on Satellite.
The record
- CVE
- CVE-2024-4871
- Published
- May 14, 2024
- Updated
- Feb 25, 2026
- Vendor
- The Foreman Project
- Product
- Foreman
- Classifications
- CWE-322, T1557
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.9.1.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo