CVE-2024-52282

Rancher Helm Applications may have sensitive values leaked

A vulnerability has been identified within Rancher Manager whereby applications installed via Rancher Manager Apps Catalog store their Helm values directly into the Apps Custom Resource Definition, resulting in any users with GET access to it to be able to read any sensitive information that are contained within the Apps’ values. Additionally, the same information leaks into auditing logs when the audit level is set to equal or above 2.

Application charts without sensitive data are not affected by this vulnerability.
This vulnerability impacts any Helm applications installed on a Rancher Manager cluster, regardless of it being installed via the Marketplace or using the helm cli.

Please consult the associated MITRE ATT&CK - Technique - Exploitation for Privilege Escalation for further information about this category of attack.

CVE-2024-52282 has a CVSS score of 6.2 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.8.10, 2.9.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched versions include Rancher Manager 2.9.5 and 2.8.10. The fix ensures that all Helm values for each App are stored as Kubernetes Secrets. After the upgrade, users are recommended to rotate passwords and secrets that may have been leaked while using the affected versions.

1. What is CVE-2024-52282? CVE-2024-52282 is a medium-severity security vulnerability in github.com/rancher/rancher (go), affecting versions >= 2.8.0, < 2.8.10. It is fixed in 2.8.10, 2.9.4.
2. How severe is CVE-2024-52282? CVE-2024-52282 has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/rancher/rancher are affected by CVE-2024-52282? github.com/rancher/rancher (go) versions >= 2.8.0, < 2.8.10 is affected.
4. Is there a fix for CVE-2024-52282? Yes. CVE-2024-52282 is fixed in 2.8.10, 2.9.4. Upgrade to this version or later.
5. Is CVE-2024-52282 exploitable, and should I be worried? Whether CVE-2024-52282 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-52282 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-52282?
   • Upgrade github.com/rancher/rancher to 2.8.10 or later
   • Upgrade github.com/rancher/rancher to 2.9.4 or later

Other vulnerabilities in github.com/rancher/rancher