Foreman: foreman: arbitrary code execution via safemode sandbox bypass
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in Foreman. This vulnerability allows an authenticated remote attacker with low-level read permissions to achieve arbitrary code execution on the underlying server. By manipulating the permitted methods list within the template rendering engine, an attacker can bypass the safemode sandbox isolation and execute unauthorized commands directly on the host system.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- Record last updated
Affected versions
- rubygem-safemode
Version range not reported
- rubygem-safemode
Version range not reported
- foreman
Version range not reported
- python-dynaconf
Version range not reported
- python-gitpython
Version range not reported
- python-lxml
Version range not reported
- python-sqlparse
Version range not reported
- rubygem-foreman_remote_execution
Version range not reported
- rubygem-hammer_cli
Version range not reported
- rubygem-katello
Version range not reported
- rubygem-safemode
Version range not reported
- satellite
Version range not reported
- yggdrasil-worker-forwarder
Version range not reported
- rubygem-safemode
Version range not reported
- foreman
Version range not reported