dbcve.org
Advanced Cluster Management For KubernetesApplication · Redhat

CVE-2020-25655

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
An issue was discovered in ManagedClusterView API, that could allow secrets to be disclosed to users without the correct permissions. Views created for an admin user would be made available for a short time to users with only view permission. In this short time window the user with view permission could read cluster secrets that should only be disclosed to admin users.

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

The ManagedClusterView API had a time-of-check-to-time-of-use (TOCTOU) vulnerability where admin-created views remained accessible in a short-lived cache to users with only view permissions, allowing unauthorized disclosure of cluster secrets.

MitigationApply the vendor patch to ensure ManagedClusterView API properly invalidates and isolates admin views from non-admin users, with authorization checks enforced at every access point.

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
Advanced Cluster Management For KubernetesApplication
Affected:= 2.0

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify if Red Hat Advanced Cluster Management for Kubernetes 2.0 is installed
    Run 'oc get csv -A | grep advanced-cluster-management' or check the operator catalog for the 'advanced-cluster-management' operator at version 2.0
    Affected if The product version shows 2.0 of Red Hat Advanced Cluster Management for Kubernetes
  2. Check for existing ManagedClusterView resources
    Run 'oc get managedclusterviews -A' to list any ManagedClusterView objects in the cluster
    Affected if ManagedClusterView resources exist in any namespace, indicating the vulnerable API is in use
  3. Verify authorization policies for ManagedClusterView access
    Examine ClusterRoleBindings and RoleBindings related to ManagedClusterView: run 'oc get clusterrolebinding -o wide' and check for roles granting 'get' or 'list' on 'managedclusterviews' to non-admin users
    Affected if Users with only 'view' permissions on ManagedClusterView resources are able to list or get these resources
  4. Test cache behavior with non-admin view user
    Create a test user with only 'view' role in a namespace, then create a ManagedClusterView as an admin, then query that view as the test user to observe if cached admin views remain accessible
    Affected if A user with only view permissions can retrieve a ManagedClusterView that was created by an admin user, indicating the TOCTOU cache vulnerability is present

A user is affected if they have RH ACM 2.0 installed with ManagedClusterView resources accessible to users with view-only permissions, allowing cached admin-created views to leak to non-admin users.

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

Apply the vendor patch to ensure ManagedClusterView API properly invalidates and isolates admin views from non-admin users, with authorization checks enforced at every access point.

Fix this in Advanced Cluster Management For Kubernetes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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