GHSA-wm2r-rp98-8pmh: Github.com/rancher/rancher Exposure Of SSH Credentials Vulnerability

LOW
CWE-200
Published
Advisory Summary

GHSA-wm2r-rp98-8pmh is a LOW exposure of ssh credentials vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Github.com/rancher/rancher libraries in the Go ecosystem. The issue involves exposure of ssh credentials in rancher/fleet. Remediation is available by upgrading affected packages to version 2.5.13, 2.6.4.

GHSA-wm2r-rp98-8pmh at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-wm2r-rp98-8pmh
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Github.com/rancher/rancher
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-wm2r-rp98-8pmh

To remediate this vulnerability, upgrade all affected Github.com/rancher/rancher dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rancher/rancher fixed: 2.5.13
Upgrade github.com/rancher/rancher to 2.5.13
github.com/rancher/rancher fixed: 2.6.4
Upgrade github.com/rancher/rancher to 2.6.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rancher/rancher

How to Check if You Are Affected

To determine whether your application is affected by GHSA-wm2r-rp98-8pmh, inspect your project dependencies for Github.com/rancher/rancher:

inspect dependencies for github.com/rancher/rancher

Analyze the terminal output to locate any version of Github.com/rancher/rancher in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.13), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Github.com/rancher/rancher, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact This vulnerability only affects customers using Fleet for continuous delivery with authenticated Git and/or Helm repositories. A security vulnerability ([CVE-2022-29810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29810)) was discovered in `go-getter` library in versions prior to [`v1.5.11`](https://github.com/hashicorp/go-getter/releases/tag/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`](https://github.com/rancher/fleet/releases/tag/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](https://rancher.com/docs/rancher/v2.6/en/deploy-across-clusters/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. ### Patches Patched versions include releases 2.5.13, 2.6.4 and later versions. ### 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](https://github.com/rancher/rancher/security/policy) for security related inquiries. * Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. * Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

GHSA-wm2r-rp98-8pmh Affected Github.com/rancher/rancher Versions

2 component(s)
Fixed Versions:
2.5.132.6.4
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rancher/rancher
Go
< 2.5.13
2.5.13
github.com/rancher/rancher
Go
≥ 2.6.0
< 2.6.4
2.6.4

References

Frequently Asked Questions

What is GHSA-wm2r-rp98-8pmh?
GHSA-wm2r-rp98-8pmh is a security vulnerability in Github.com/rancher/rancher involving Exposure of SSH credentials in Rancher/Fleet under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Github.com/rancher/rancher versions are affected?
Affected versions include releases prior to 2.5.13, 2.6.4 across affected packages: github.com/rancher/rancher.
What version fixes GHSA-wm2r-rp98-8pmh?
Upgrading to 2.5.13, 2.6.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rancher/rancher affected?
Yes, github.com/rancher/rancher is affected in releases prior to 2.5.13, 2.6.4. Upgrade your dependency to 2.5.13, 2.6.4 or later.
What CWE is associated with GHSA-wm2r-rp98-8pmh?
GHSA-wm2r-rp98-8pmh is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for GHSA-wm2r-rp98-8pmh?
Run the dependency tree command: 'inspect dependencies for github.com/rancher/rancher'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wm2r-rp98-8pmh",
  "modified" : "2022-04-27T21:09:13Z",
  "published" : "2022-04-27T21:09:13Z",
  "aliases" : [ ],
  "summary" : "Exposure of SSH credentials in Rancher/Fleet",
  "details" : "### Impact\nThis vulnerability only affects customers using Fleet for continuous delivery with authenticated Git and/or Helm repositories.\n\nA security vulnerability ([CVE-2022-29810](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29810)) was discovered in `go-getter` library in versions prior to [`v1.5.11`](https://github.com/hashicorp/go-getter/releases/tag/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`](https://github.com/rancher/fleet/releases/tag/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.\n\nWhen Git and/or Helm authentication is configured in [Fleet](https://rancher.com/docs/rancher/v2.6/en/deploy-across-clusters/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.\n\n### Patches\nPatched versions include releases 2.5.13, 2.6.4 and later versions.\n\n### Workarounds\nThere 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.\n\n**Note:** If you believe that SSH keys might have been exposed in your environment, it's highly advised to rotate them.\n\n### Credits\nThis issue was found and reported by Dagan Henderson from Raft Engineering.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n* Verify our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.5.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/rancher"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.6.0"
      }, {
        "fixed" : "2.6.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rancher/rancher/security/advisories/GHSA-wm2r-rp98-8pmh"
  }, {
    "type" : "PACKAGE",
    "url" : "github.com/rancher/rancher"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-04-27T21:09:13Z",
    "nvd_published_at" : null
  }
}