Summary
Exposure of SSH credentials in Rancher/Fleet
Workarounds
There is not a direct mitigation besides upgrading to the patched Rancher versions. Until you are able to upgrade, limit access in Rancher to trusted users and carefully validate the URLs you are using are correct. Please note that the SSH key might still be compromised in valid URLs if the service goes down or a connection error happens when pulling from the repos.
Note: If you believe that SSH keys might have been exposed in your environment, it's highly advised to rotate them.
Credits
This issue was found and reported by Dagan Henderson from Raft Engineering.
For more information
If you have any questions or comments about this advisory:
- Reach out to SUSE Rancher Security team for security related inquiries.
- Open an issue in Rancher repository.
- Verify our support matrix and product support lifecycle.
Impact
This vulnerability only affects customers using Fleet for continuous delivery with authenticated Git and/or Helm repositories.
A security vulnerability (CVE-2022-29810) was discovered in go-getter library in versions prior to v1.5.11 that exposes SSH private keys in base64 format due to a failure in redacting such information from error messages. The vulnerable version of this library is used in Rancher through Fleet in versions of Fleet prior to v0.3.9. This issue affects Rancher versions 2.5.0 up to and including 2.5.12 and from 2.6.0 up to and including 2.6.3.
When Git and/or Helm authentication is configured in Fleet and Fleet is used to deploy a git repo through Continuous Delivery, the affected go-getter version will expose the configured SSH private key secret if Fleet fails to download the git repo due to a misconfigured URL. The exposed SSH key is logged in base64 format as a query parameter together with the git URL. The credentials can be seen in Rancher UI and in Fleet's deployment pod logs.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Patched versions include releases 2.5.13, 2.6.4 and later versions.
Frequently Asked Questions
- What is GHSA-WM2R-RP98-8PMH? GHSA-WM2R-RP98-8PMH is a low-severity security vulnerability in github.com/rancher/rancher (go), affecting versions < 2.5.13. It is fixed in 2.5.13, 2.6.4.
- Which versions of github.com/rancher/rancher are affected by GHSA-WM2R-RP98-8PMH? github.com/rancher/rancher (go) versions < 2.5.13 is affected.
- Is there a fix for GHSA-WM2R-RP98-8PMH? Yes. GHSA-WM2R-RP98-8PMH is fixed in 2.5.13, 2.6.4. Upgrade to this version or later.
- Is GHSA-WM2R-RP98-8PMH exploitable, and should I be worried? Whether GHSA-WM2R-RP98-8PMH 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
- What actually determines whether GHSA-WM2R-RP98-8PMH 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.
- How do I fix GHSA-WM2R-RP98-8PMH?
- Upgrade
github.com/rancher/rancherto 2.5.13 or later - Upgrade
github.com/rancher/rancherto 2.6.4 or later
- Upgrade