GHSA-46v3-ggjg-qq3x

Suggest an improvement
Source
https://github.com/advisories/GHSA-46v3-ggjg-qq3x
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/06/GHSA-46v3-ggjg-qq3x/GHSA-46v3-ggjg-qq3x.json
JSON Data
https://api.test.osv.dev/v1/vulns/GHSA-46v3-ggjg-qq3x
Aliases
Related
Published
2023-06-06T01:59:54Z
Modified
2024-09-16T15:05:11Z
Severity
  • 8.4 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H CVSS Calculator
  • 6.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H CVSS Calculator
Summary
Rancher UI has multiple Cross-Site Scripting (XSS) issues
Details

Impact

Multiple Cross-Site Scripting (XSS) vulnerabilities have been identified in the Rancher UI. Cross-Site scripting allows a malicious user to inject code that is executed within another user's browser, allowing the attacker to steal sensitive information, manipulate web content, or perform other malicious activities on behalf of the victims. This could result in a user with write access to the affected areas being able to act on behalf of an administrator, once an administrator opens the affected web page.

The affected areas include the Projects/Namespaces and Auth Provider sections. The attacker needs to be authenticated and have write access to those features in order to exploit the vulnerabilities. Some of the permissions (roles) required are:

  • Project Owner.
  • Restricted Admin.
  • Configure Authentication.
  • Administrator.
  • Custom RBAC Role that provides write access on Projects or External Authentication Providers.

For users that suspect this vulnerability may have targeted their Rancher instance, we recommend rotating all API Keys and Kubeconfig tokens.

It's also advised to review logs and possibly rotate credentials stored as secrets in Rancher and downstream cluster, if you believe that users' credentials to access Rancher and its clusters might have been compromised.

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.

Credits

We would like to recognize and thank @bybit-sec for the responsible disclosure of this security issue.

For more information

If you have any questions or comments about this advisory:

Database specific
{
    "cwe_ids": [
        "CWE-79"
    ],
    "github_reviewed_at": "2023-06-06T01:59:54Z",
    "nvd_published_at": "2023-06-01T13:15:10Z",
    "severity": "MODERATE",
    "github_reviewed": true
}
References

Affected packages

Go / github.com/rancher/rancher

Package

Name
github.com/rancher/rancher
View open source insights on deps.dev
Purl
pkg:golang/github.com/rancher/rancher

Affected ranges

Type
SEMVER
Events
Introduced
2.6.0
Fixed
2.6.13

Go / github.com/rancher/rancher

Package

Name
github.com/rancher/rancher
View open source insights on deps.dev
Purl
pkg:golang/github.com/rancher/rancher

Affected ranges

Type
SEMVER
Events
Introduced
2.7.0
Fixed
2.7.4