dbcve.org
ForemanfogproxmoxApplication · Theforeman

CVE-2021-20259

HIGH · 7.8 CVSS v3.1 Published 2021-06-07
Fix available
A fix is available. Upgrade to 0.13.1 or later.
See remediation →
80/100
Remediation priority · High
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 flaw was found in the Foreman project. The Proxmox compute resource exposes the password through the API to an authenticated local attacker with view_hosts permission. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Versions before foreman_fog_proxmox 0.13.1 are affected

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

The Foreman Proxmox compute resource exposes Proxmox passwords through the API to any authenticated local attacker with view_hosts permission, allowing unauthorized access to Proxmox infrastructure credentials.

MitigationUpgrade foreman_fog_proxmox to version 0.13.1 or later to remediate the credential exposure vulnerability.

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
ForemanfogproxmoxApplication
Affected:< 0.13.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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. Check foreman_fog_proxmox plugin version
    Run 'gem list foreman_fog_proxmox' or check the plugin version in Foreman's UI under Administer > About > Plugins
    Affected if Installed version is lower than 0.13.1
  2. Identify Proxmox compute resources
    In Foreman UI, navigate to Infrastructure > Compute Resources or use API call GET /api/compute_resources - look for Proxmox providers
    Affected if Any Proxmox compute resource exists in the environment
  3. Verify view_hosts permission exists
    Check Foreman user roles and permissions: navigate to Administer > Users > (select user) > Roles, or query the API for users with view_hosts permission
    Affected if Any user role includes the view_hosts permission
  4. Test API credential exposure
    As an authenticated user with view_hosts permission, query the compute resource API endpoint (GET /api/compute_resources/:id) for a Proxmox resource and inspect if the password field is returned in plaintext
    Affected if API response includes plaintext Proxmox password in the compute resource attributes

Environment is affected if foreman_fog_proxmox version is below 0.13.1 AND Proxmox compute resources are configured AND users with view_hosts permission exist in Foreman.

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
Upgrade available Upgrade to 0.13.1 or later
Fixed in 0.13.1
Interim mitigation

Upgrade foreman_fog_proxmox to version 0.13.1 or later to remediate the credential exposure vulnerability.

Fix this in Foremanfogproxmox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20259 — 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-2021-20259 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