dbcve.org
RancherApplication · Suse

CVE-2020-10676

HIGH · 8.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 2.6.13 / 2.7.4 or later.
See remediation →
94/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
In Rancher 2.x before 2.6.13 and 2.7.x before 2.7.4, an incorrectly applied authorization check allows users who have certain access to a namespace to move that namespace to a different project.

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

Rancher 2.x contains an authorization bypass where users with certain access to a namespace can move that namespace to a different project. This incorrectly applied authorization check allows namespace-level users to perform what should be project-level or higher privileged operations, enabling potential privilege escalation or resource isolation bypass.

MitigationUpgrade Rancher to version 2.6.13 or later, or 2.7.4 or later to receive the patched authorization checks. Alternatively, audit namespace-to-project assignments and restrict namespace move capabilities until patching is completed.

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
RancherApplication
Affected:>= 2.0.0, < 2.6.13>= 2.7.0, < 2.7.4

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
High

CVSS:3.1/AV:N/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. Identify Rancher version
    Run 'rancher --version' or check the Helm chart version with 'helm list -n cattle-system' and inspect the image tags in the deployment
    Affected if The installed version falls within >= 2.0.0 to < 2.6.13 OR >= 2.7.0 to < 2.7.4
  2. Verify namespace move capability exists
    In Rancher UI, go to a project, select a namespace, and check if there is an option or API endpoint to move the namespace to a different project. Alternatively, query the Kubernetes API: 'kubectl auth can-i update --subresource=status -n <namespace>' for a namespace-level user
    Affected if Namespace-level users have permissions that allow moving namespaces between projects
  3. Review namespace-to-project assignments
    List all namespaces and their assigned projects using the Rancher API or UI: GET /v3/projects/{projectID}/namespaces. Check if any namespaces are assigned to projects that their users should not have access to
    Affected if Namespaces are assigned to projects outside of expected boundaries, suggesting unauthorized moves may have occurred
  4. Audit user role bindings
    Check which users have access to specific namespaces: 'kubectl get rolebindings -A -o json' and identify users with namespace-level permissions who could potentially move resources
    Affected if Users with only namespace-level roles exist in the environment, creating the precondition for this bypass
  5. Check for unusual namespace movements
    Review Rancher audit logs or Kubernetes events for namespace resource changes. Look for operations on the namespace project assignment property, or check API server logs for PATCH/POST requests to namespace project endpoints
    Affected if Historical records show namespace project reassignments performed by users who should only have namespace-level permissions

You are affected if your Rancher version is between 2.0.0 and 2.6.12, or between 2.7.0 and 2.7.3, AND namespace-level users have the ability to move namespaces to different projects.

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.

dbcve · scoped
Upgrade available Upgrade to 2.6.13 / 2.7.4 or later
Fixed in 2.6.132.7.4
Interim mitigation

Upgrade Rancher to version 2.6.13 or later, or 2.7.4 or later to receive the patched authorization checks. Alternatively, audit namespace-to-project assignments and restrict namespace move capabilities until patching is completed.

Recommended fix Moderate confidence

Rancher 2.6.13+ or 2.7.4+ (depending on your current major/minor version branch)

  1. Backup your Rancher environment before proceeding with any upgrade
  2. If running Rancher 2.6.x (2.0.0 to 2.6.12), upgrade to Rancher 2.6.13 or later
  3. If running Rancher 2.7.x (2.7.0 to 2.7.3), upgrade to Rancher 2.7.4 or later
  4. After upgrade, verify that users with namespace access can no longer move namespaces to arbitrary projects (the authorization check should now be correctly enforced)
  5. Consult Rancher release notes for any known issues specific to your target version
Caveat Review Rancher release notes between your current version and target version for any migration considerations or deprecated features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rancher 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-10676 — 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-10676 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