dbcve.org
SatelliteApplication · Redhat

CVE-2022-3874

CRITICAL · 9.1 CVSS v3.1 Published 2023-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A command injection flaw was found in foreman. This flaw allows an authenticated user with admin privileges on the foreman instance to transpile commands through CoreOS and Fedora CoreOS configurations in templates, possibly resulting in arbitrary command execution on the underlying operating system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A command injection vulnerability in Foreman allows authenticated administrators to execute arbitrary OS commands through CoreOS and Fedora CoreOS configuration templates. The flaw exists in the template transpilation process where user-supplied input in templates is not properly sanitized before being passed to the underlying system for execution.

MitigationImmediately restrict admin access to only trusted personnel and review existing templates for malicious content. Apply vendor patches when released and consider implementing template sandboxing or input validation controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SatelliteApplication
Affected:= 6.0
ForemanApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Foreman or Red Hat Satellite installation
    Run 'foreman --version' or 'satellite --version' to determine if the software is present and get the version number.
    Affected if Version is Foreman any version OR Red Hat Satellite 6.0 specifically.
  2. Verify authenticated administrator access exists
    Check user accounts with administrator privileges in Foreman via 'hammer user list --admin true' or through the Foreman web UI under Administer > Users.
    Affected if Any user account has administrator-level privileges in Foreman.
  3. Identify CoreOS or Fedora CoreOS configuration templates
    Navigate to Hosts > Provisioning Templates in the Foreman UI, or use 'hammer template list' to list all templates. Look for templates with names containing 'coreos', 'fedora-coreos', or 'fcos'.
    Affected if CoreOS, Fedora CoreOS, or FCOS provisioning templates are present in the system.
  4. Inspect template transpilation configuration
    Examine the identified CoreOS templates for any embedded shell commands, variable substitutions using ERB syntax ({{ vm.rhelSubscriptionUsername }}), or script blocks that could contain unsanitized user input.
    Affected if Templates contain ERB variable interpolations or shell script fragments that process user-supplied values without sanitization.
  5. Review recent template modifications
    Check template audit logs via Foreman UI (Monitor > Audits) or database query for recent changes to CoreOS templates by administrators.
    Affected if Templates were recently modified, especially by accounts that should not have admin access or that show unusual activity patterns.

A user is affected if they have Foreman or Red Hat Satellite 6.0 running with any authenticated administrator accounts and CoreOS/Fedora CoreOS provisioning templates in active use, as this combination enables the command injection attack surface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict admin access to only trusted personnel and review existing templates for malicious content. Apply vendor patches when released and consider implementing template sandboxing or input validation controls.

Fix this in Satellite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3874 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data