Log in Start free

Vulnerability · Published May 14, 2024 · Assigned by redhat

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

Medium 6.8

In plain English

A medium-severity security flaw in foreman. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 49% of all known vulnerabilities).

Severity (CVSS 3.1)6.8Medium
Exploit odds (30 days)0.6%top 50.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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

Affected products (as reported)

VendorProductVersions
foreman 3.9.1.8
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references
Red Hat Red Hat Satellite 6.15 for RHEL 8 see references

Weakness: CWE-322 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

References