CVE-2020-10676: Github.com/rancher/rancher Rancher Users Retain Access After Vulnerability

HIGH
Advisory Identifier: GHSA-8vhc-hwhc-cpj4
CVSS 8.8
CWE-863
Published
Advisory Summary

CVE-2020-10676 is a HIGH (CVSS 8.8) rancher users retain access after vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/rancher/rancher libraries in the Go ecosystem. The issue involves rancher users retain access after moving namespaces into projects they don't have access to. Remediation is available by upgrading affected packages to version 2.6.13, 2.7.4.

CVE-2020-10676 at a Glance

CVE Identifier CVE-2020-10676
GHSA Identifier GHSA-8vhc-hwhc-cpj4
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/rancher/rancher
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2020-10676

To remediate this vulnerability, upgrade all affected Github.com/rancher/rancher dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rancher/rancher fixed: 2.6.13
Upgrade github.com/rancher/rancher to 2.6.13
github.com/rancher/rancher fixed: 2.7.4
Upgrade github.com/rancher/rancher to 2.7.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rancher/rancher

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-10676, inspect your project dependencies for Github.com/rancher/rancher:

inspect dependencies for github.com/rancher/rancher

Analyze the terminal output to locate any version of Github.com/rancher/rancher in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.6.13), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/rancher/rancher, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A vulnerability was identified in which users with update privileges on a namespace, can move that namespace into a project they don't have access to. After the namespace transfer is completed, their previous permissions are still preserved, which enables them to gain access to project-specific resources (such as [project secrets](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets#creating-secrets-in-projects)). In addition, resources in the namespace will now count toward the [quota limit](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas) of the new project, potentially causing availability issues. User with roles `Project Owner` and `Project Member` on the source project can exploit this vulnerability; however, this would also apply to custom roles with similar privileges. The patched version include an improved RBAC mechanism, which checks if the user has the correct permissions before the namespace move takes place. ### Patches Patched versions include releases `2.6.13`, `2.7.4` and later versions. ### Workarounds There is no direct mitigation besides updating Rancher to a patched version. ### For more information If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

CVE-2020-10676 Affected Github.com/rancher/rancher Versions

2 component(s)
Fixed Versions:
2.6.132.7.4
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rancher/rancher
Go
≥ 2.6.0
< 2.6.13
2.6.13
github.com/rancher/rancher
Go
≥ 2.7.0
< 2.7.4
2.7.4

References

Frequently Asked Questions

What is CVE-2020-10676?
CVE-2020-10676 is a security vulnerability in Github.com/rancher/rancher involving Rancher users retain access after moving namespaces into projects they don't have access to under CWE-863: Incorrect Authorization.
Which Github.com/rancher/rancher versions are affected?
Affected versions include releases prior to 2.6.13, 2.7.4 across affected packages: github.com/rancher/rancher.
What version fixes CVE-2020-10676?
Upgrading to 2.6.13, 2.7.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rancher/rancher affected?
Yes, github.com/rancher/rancher is affected in releases prior to 2.6.13, 2.7.4. Upgrade your dependency to 2.6.13, 2.7.4 or later.
What is the CVSS score of CVE-2020-10676?
CVE-2020-10676 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2020-10676?
CVE-2020-10676 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2020-10676?
Run the dependency tree command: 'inspect dependencies for github.com/rancher/rancher'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8vhc-hwhc-cpj4",
  "modified" : "2023-12-12T19:44:59Z",
  "published" : "2023-06-06T01:59:31Z",
  "aliases" : [ "CVE-2020-10676" ],
  "summary" : "Rancher users retain access after moving namespaces into projects they don't have access to",
  "details" : "### Impact\nA vulnerability was identified in which users with update privileges on a namespace, can move that namespace into a project they don't have access to. After the namespace transfer is completed, their previous permissions are still preserved, which enables them to gain access to project-specific resources (such as [project secrets](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-resources-setup/secrets#creating-secrets-in-projects)). In addition, resources in the namespace will now count toward the [quota limit](https://ranchermanager.docs.rancher.com/how-to-guides/advanced-user-guides/manage-projects/manage-project-resource-quotas/about-project-resource-quotas) of the new project, potentially causing availability issues.\n\nUser with roles `Project Owner` and `Project Member` on the source project can exploit this vulnerability; however, this would also apply to custom roles with similar privileges. \n\nThe patched version include an improved RBAC mechanism, which checks if the user has the correct permissions before the namespace move takes place.\n\n### Patches\nPatched versions include releases `2.6.13`, `2.7.4` and later versions.\n\n### Workarounds\nThere is no direct mitigation besides updating Rancher to a patched version.\n\n### For more information\nIf you have any questions or comments about this advisory:\n\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.6.0"
      }, {
        "fixed" : "2.6.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.7.0"
      }, {
        "fixed" : "2.7.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/security/advisories/GHSA-8vhc-hwhc-cpj4"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-10676"
  }, {
    "type" : "WEB",
    "url" : "https://forums.rancher.com/c/announcements"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-8vhc-hwhc-cpj4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rancher/rancher"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/releases/tag/v2.6.13"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/releases/tag/v2.7.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-06-06T01:59:31Z",
    "nvd_published_at" : "2023-12-12T17:15:07Z"
  }
}