CloudformsApplication · Redhat

CVE-2020-25716

HIGH · 8.1 CVSS v3.1 Published 2021-06-07
Fix available
A fix is available. Upgrade to 5.11.10.1 or later.
See remediation →
87/100
Remediation priority · High
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 flaw was found in Cloudforms. A role-based privileges escalation flaw where export or import of administrator files is possible. An attacker with a specific group can perform actions restricted only to system administrator. This is the affect of an incomplete fix for CVE-2020-10783. The highest threat from this vulnerability is to data confidentiality and integrity. Versions before cfme 5.11.10.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 · high confidence

A role-based privilege escalation vulnerability in Red Hat CloudForms allows users with a specific group membership to export or import administrator files, bypassing intended access restrictions. This represents an incomplete fix for CVE-2020-10783, where the original patch failed to fully address privilege boundary checks. Attackers can perform system administrator actions despite having limited group permissions.

MitigationUpgrade to cfme version 5.11.10.1 or later which contains the complete fix for this privilege escalation 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
CloudformsApplication
Affected:< 5.11.10.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 installed CloudForms version
    Run 'rpm -q cfme' or access the CloudForms web UI, navigate to About > Diagnostics > Server and look for the CFME version number
    Affected if The installed version is lower than 5.11.10.1 (e.g., 5.11.9.0, 5.11.8.0, etc.)
  2. Identify users with limited group membership
    In the CloudForms web UI, go to Configuration > Access Control > Groups and review all group memberships. Note users assigned to non-administrator groups
    Affected if Users with limited group permissions exist in the system who could potentially exploit the privilege escalation
  3. Verify export/import feature permissions
    In the CloudForms web UI, go to Configuration > Access Control > Roles and examine role settings for each role. Check if any limited-roles have export or import capabilities enabled under the dialog features section
    Affected if Non-administrator roles have export or import features enabled that should be restricted
  4. Review role-to-group assignments
    In Configuration > Access Control, cross-reference which groups are assigned to roles with export/import capabilities. Identify if limited groups have elevated import/export access
    Affected if Users in limited groups can access export/import functionality that should be restricted to administrator roles

Your environment is affected if the installed CloudForms version is below 5.11.10.1 AND non-administrator users with limited group permissions can access export or import features.

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 5.11.10.1 or later
Fixed in 5.11.10.1
Interim mitigation

Upgrade to cfme version 5.11.10.1 or later which contains the complete fix for this privilege escalation vulnerability.

Fix this in Cloudforms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25716 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25716 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