SatelliteApplication · Redhat
CVE-2023-0462
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 · uneditedAn arbitrary code execution flaw was found in Foreman. This issue may allow an admin user to execute arbitrary code on the underlying operating system by setting global parameters with a YAML payload.
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 · high confidenceA code injection vulnerability in Foreman allows authenticated admin users to achieve arbitrary OS command execution by embedding malicious payloads in global parameters that get parsed as YAML code. The vulnerability stems from unsafe deserialization of YAML input in the global parameter handling functionality.
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
>= 6.0< 3.8.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Foreman versionRun 'foreman --version' or check the About page in the Foreman web UI under Administer > About. For Red Hat Satellite, run 'satellite-installer --version' or check the version via 'rpm -q satellite'.Affected if Installed version is Foreman < 3.8.0 or Red Hat Satellite >= 6.0
-
Identify if global parameters are configuredNavigate to Configure > Global Parameters in the Foreman web UI, or query the API endpoint /api/v2/common_parameters. Check if any parameters exist.Affected if Global parameters are defined in the system
-
Verify YAML parsing is enabled for parametersInspect the Foreman settings database table 'settings' for the setting named 'yaml' or 'safemode' under the 'Param' category, or check config/foreman.yml for yaml pipeline settings.Affected if YAML deserialization of global parameter values is not disabled in settings
-
Check for admin role assignmentsReview User > Users and User > User Groups in the Foreman web UI. Identify which users have the Admin role assigned. Check the auth_source and admin flag in the users database table.Affected if Any user account with admin privileges exists in the system
Your environment is affected if you run Foreman < 3.8.0 or Red Hat Satellite >= 6.0, have global parameters configured, and have at least one admin user account enabled.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped3.8.0
Restrict or disable YAML parsing of user-supplied global parameter values, implement proper input validation/sanitization, or apply vendor patches. Consider least-privilege admin access controls as a compensating control.
Foreman 3.8.0 or later
- Backup Foreman database and configuration before upgrade
- Review Foreman 3.8.0 release notes for any breaking changes or required migration steps
- Upgrade Foreman to version 3.8.0 or later
- After upgrade, verify that global parameters can no longer accept YAML payloads that execute arbitrary code
- Test that normal Foreman functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Satellite
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0462 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-0462 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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