Skip to content
Noroxi
CVE-2024-4871· NVD / CVE Program· CNA redhat

Foreman: host ssh key not being checked in remote execution

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.61% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: foreman (Red Hat:satellite_capsule:6.15::el8) 0:3.9.1.8-1.el8sat; foreman-debug (Red Hat:satellite_capsule:6.15::el8) 0:3.9.1.8-1.el8sat; foreman-installer (Red Hat:satellite_capsule:6.15::el8) 1:3.9.3.2-1.el8sat.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to foreman (Red Hat:satellite_capsule:6.15::el8) 0:3.9.1.8-1.el8sat; foreman-debug (Red Hat:satellite_capsule:6.15::el8) 0:3.9.1.8-1.el8sat; foreman-installer (Red Hat:satellite_capsule:6.15::el8) 1:3.9.3.2-1.el8sat or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.8 · v3.1—No exploit Fix available
Published
May 14, 2024
Updated
Jun 17, 2026
EPSS
0.6% · 48th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
27 / 40 · 6.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
6.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-4871

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for red hat records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • github.com/theforeman/foreman foreman

    • 3.9.1.8affected

  • Red Hat Red Hat Satellite 6.15 for RHEL 8

    • 0:4.3.14-1.el8sat and laternot affected · rpm
    • 0:3.9.1.8-1.el8sat and laternot affected · rpm
    • 1:3.9.3.2-1.el8sat and laternot affected · rpm
    • 0:2.16.9-1.el8pc and laternot affected · rpm
    • 0:3.39.15-1.el8pc and laternot affected · rpm
    • 0:1.8.3-1.el8sat and laternot affected · rpm
    • 0:13.0.6-1.el8sat and laternot affected · rpm
    • 0:12.0.7-1.el8sat and laternot affected · rpm
    • 0:4.11.0.15-1.el8sat and laternot affected · rpm
    • 0:3.0.0-1.el8sat and laternot affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:satellite_capsule:6.15::el8foremanbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite_capsule:6.15::el8foreman-debugbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite_capsule:6.15::el8foreman-installerbefore 1:3.9.3.2-1.el8sat1:3.9.3.2-1.el8sat
Red Hat:satellite_capsule:6.15::el8foreman-installer-katellobefore 1:3.9.3.2-1.el8sat1:3.9.3.2-1.el8sat
Red Hat:satellite_capsule:6.15::el8python-pulp-containerbefore 0:2.16.9-1.el8pc0:2.16.9-1.el8pc
Red Hat:satellite_capsule:6.15::el8python-pulpcorebefore 0:3.39.15-1.el8pc0:3.39.15-1.el8pc
Red Hat:satellite_capsule:6.15::el8python3.11-pulp-containerbefore 0:2.16.9-1.el8pc0:2.16.9-1.el8pc
Red Hat:satellite_capsule:6.15::el8python3.11-pulpcorebefore 0:3.39.15-1.el8pc0:3.39.15-1.el8pc
Red Hat:satellite_capsule:6.15::el8rubygem-dynflowbefore 0:1.8.3-1.el8sat0:1.8.3-1.el8sat
Red Hat:satellite_capsule:6.15::el8rubygem-smart_proxy_container_gatewaybefore 0:3.0.0-1.el8sat0:3.0.0-1.el8sat
Red Hat:satellite_capsule:6.15::el8rubygem-smart_proxy_remote_execution_sshbefore 0:0.10.6-1.el8sat0:0.10.6-1.el8sat
Red Hat:satellite_capsule:6.15::el8satellitebefore 0:6.15.2-1.el8sat0:6.15.2-1.el8sat
Red Hat:satellite_capsule:6.15::el8satellite-capsulebefore 0:6.15.2-1.el8sat0:6.15.2-1.el8sat
Red Hat:satellite_capsule:6.15::el8satellite-commonbefore 0:6.15.2-1.el8sat0:6.15.2-1.el8sat
Red Hat:satellite_utils:6.15::el8foreman-clibefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite_utils:6.15::el8satellite-clibefore 0:6.15.2-1.el8sat0:6.15.2-1.el8sat
Red Hat:satellite:6.15::el8candlepinbefore 0:4.3.14-1.el8sat0:4.3.14-1.el8sat
Red Hat:satellite:6.15::el8candlepin-selinuxbefore 0:4.3.14-1.el8sat0:4.3.14-1.el8sat
Red Hat:satellite:6.15::el8foreman-dynflow-sidekiqbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite:6.15::el8foreman-ec2before 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite:6.15::el8foreman-journaldbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite:6.15::el8foreman-libvirtbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite:6.15::el8foreman-openstackbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat
Red Hat:satellite:6.15::el8foreman-ovirtbefore 0:3.9.1.8-1.el8sat0:3.9.1.8-1.el8sat

+10

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:foreman0:3.9.1.8-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:foreman-debug0:3.9.1.8-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:foreman-installer1:3.9.3.2-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:foreman-installer-katello1:3.9.3.2-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:python-pulp-container0:2.16.9-1.el8pc · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:python-pulpcore0:3.39.15-1.el8pc · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:python3.11-pulp-container0:2.16.9-1.el8pc · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:python3.11-pulpcore0:3.39.15-1.el8pc · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:rubygem-dynflow0:1.8.3-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:rubygem-smart_proxy_container_gateway0:3.0.0-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:rubygem-smart_proxy_remote_execution_ssh0:0.10.6-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)
red hat:satellite0:6.15.2-1.el8sat · Red Hat:satellite_capsule:6.15::el8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-322 · Key Exchange without Entity Authentication

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records