github.com/rancher/rancher
Affected
- introduced
2.6.0, fixed2.6.13(semver)
Fixed versions
2.6.13
Fix
- Fixed version
2.6.13go get github.com/rancher/[email protected]
Advisory
Also known as: CVE-2022-43760
Rancher UI has multiple Cross-Site Scripting (XSS) issues
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:
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:
Medium Basis: The source's own band: MODERATE
2.6.0, fixed 2.6.13 (semver)2.6.13
2.6.13go get github.com/rancher/[email protected]2.7.0, fixed 2.7.4 (semver)2.7.4
2.7.4go get github.com/rancher/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0