Skip to content

Rancher UI has Stored Cross-site Scripting vulnerability

High severity GitHub Reviewed Published Jan 14, 2025 in rancher/rancher • Updated Jan 14, 2025

Package

gomod github.com/rancher/rancher (Go)

Affected versions

>= 2.9.0, < 2.9.4

Patched versions

2.9.4

Description

Impact

A vulnerability has been identified within Rancher UI that allows a malicious actor to perform a Stored XSS attack through the cluster description field.

Please consult the associated MITRE ATT&CK - Technique - Drive-by Compromise for further information about this category of attack.

Patches

The fix introduces new changes in the directives responsible for sanitizing HTML code before rendering.

We replaced the v-tooltip directive with the v-clean-tooltip directive.

Patched versions include releases 2.9.4 and 2.10.0.

Workarounds

There are no workarounds for this issue. Users are recommended to upgrade, as soon as possible, to a version of /Rancher Manager which contains the fixes.

Credits

This issue was identified and reported by Bhavin Makwana from Workday’s Cyber Defence Team.

For more information

If you have any questions or comments about this advisory:

References

@pdellamore pdellamore published to rancher/rancher Jan 14, 2025
Published to the GitHub Advisory Database Jan 14, 2025
Reviewed Jan 14, 2025
Last updated Jan 14, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L

Weaknesses

CVE ID

CVE-2024-52281

GHSA ID

GHSA-2v2w-8v8c-wcm9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.