Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-43760

Cross-Site Scripting (XSS) in github.com/rancher/rancher (CVE-2022-43760)

Summary

Cross-site scripting in github.com/rancher/rancher (CVE-2022-43760). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.7.4 or later.

Original description

The description as published by the source.

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.

Cred…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-43760 has been found in github.com/rancher/rancher.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/rancher/rancher to 2.7.4 or later.
If unsure, ask your IT team or search "github.com/rancher/rancher CVE-2022-43760" on the vendor's site.

CVE-2022-43760 (github.com/rancher/rancher) — CWE-79
Attack vector: remote (network-reachable)
Patched: 2.7.4 — apply immediately
Workaround: There is no direct mitigation besides updating Rancher to a patched version.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in github.com/rancher/rancher.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/rancher/rancher.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.7.4.

🛡️ Workaround

Workaround: There is no direct mitigation besides updating Rancher to a patched version.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/rancher/rancher' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/rancher/rancher' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/rancher/rancher を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There is no direct mitigation besides updating Rancher to a patched version.

    パッチが適用されるまでの応急処置として、There is no direct mitigation besides updating Rancher to a patched version. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/rancher/rancher to 2.7.4

    ステージング環境で 2.7.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/rancher/rancher
[{"type":"SEMVER","events":[{"introduced":"2.7.0"},{"fixed":"2.7.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details