Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Exposure of vSphere's CPI and CSI credentials in Rancher

CVSS 3.1 9.1 CRITICALCVSS 4.0 8.5 HIGHEUVD CVSS 4.0 8.5 CVSS 4.0 · [email protected] · Secondary 8.5 HIGHCVSS 3.1 · [email protected] · Secondary 9.1 CRITICALCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/rancher/rancher 2.9.3Fixed by github.com/rancher/rancher 2.8.9osv · severity unknownKEV status unknown

cve-program · CVE-2022-45157

Published

A vulnerability has been identified in the way that Rancher stores vSphere's CPI (Cloud Provider Interface) and CSI (Container Storage Interface) credentials used to deploy clusters through the vSphere cloud provider. This issue leads to the vSphere CPI and CSI passwords being stored in a plaintext object inside Rancher. This vulnerability is only applicable to users that deploy clusters in vSphere environments.

Read the publisher's advisory

euvd · EUVD-2024-3170

Published

A vulnerability has been identified in the way that Rancher stores vSphere's CPI (Cloud Provider Interface) and CSI (Container Storage Interface) credentials used to deploy clusters through the vSphere cloud provider. This issue leads to the vSphere CPI and CSI passwords being stored in a plaintext object inside Rancher. This vulnerability is only applicable to users that deploy clusters in vSphere environments.

Read the publisher's advisory

nvd · CVE-2022-45157

Published

A vulnerability has been identified in the way that Rancher stores vSphere's CPI (Cloud Provider Interface) and CSI (Container Storage Interface) credentials used to deploy clusters through the vSphere cloud provider. This issue leads to the vSphere CPI and CSI passwords being stored in a plaintext object inside Rancher. This vulnerability is only applicable to users that deploy clusters in vSphere environments.

Read the publisher's advisory

osv · GHSA-xj7w-r753-vj8v

Published

### Impact A vulnerability has been identified in the way that Rancher stores vSphere's CPI (Cloud Provider Interface) and CSI (Container Storage Interface) credentials used to deploy clusters through the vSphere cloud provider. This issue leads to the vSphere CPI and CSI passwords being stored in a plaintext object inside Rancher. This vulnerability is only applicable to users that deploy clusters in vSphere environments. The exposed passwords were accessible in the following objects: - Can be accessed by users that are cluster members of the provisioned clusters: - When provisioning a new cluster with the vSphere cloud provider through Rancher's UI (user interface), Cluster Templates and Terraform on the object `provisioning.cattle.io` in `spec.rkeConfig.chartValues.rancher-vsphere-cpi` and `spec.rkeConfig.chartValues.rancher-vsphere-csi`. - On the object `rke.cattle.io.rkecontrolplane` in `spec.chartValues.rancher-vsphere-cpi` and `spec.chartValues.rancher-vsphere-csi`. - Can be accessed by users with privileged access to the clusters' infrastructure (host OS): - Inside the `plan` files in the provisioned downstream clusters' filesystems. **Note:** if you believe that the vSphere credentials might have been accessed by unauthorized users, it's highly recommended to change them, after updating Rancher to a patched version. Please consult the associated [MITRE ATT&CK - Technique - Credential Access](https://attack.mitre.org/tactics/TA0006/) for further information about this category of attack. ### Patches Patched versions include Rancher releases **2.8.9 and 2.9.3**. After updating your environment to one of the patched Rancher's versions, it's mandatory to execute [this script](https://github.com/rancherlabs/support-tools/tree/master/migrate-vsphere-clusters) that provides an automated way to mitigate any vulnerable leftover vSphere clusters' credentials within Rancher's local cluster. This script doesn't need to be executed in case you are installing a fresh and new environment. The script will fetch all objects in Rancher's local cluster, loops through them, if the affected vSphere charts are present, then it extracts the `username` and `password` parameters into a secret in the `fleet-default` namespace for both with the appropriate annotation to synchronize them to the downstream clusters. Finally, it updates the cluster's `chartValues` to reference those secrets rather than existing plaintext values. The script confirms on write operations, as well as backs up configurations of the cluster objects before operating so rolling back is simple. To run the script, fetch the `kubeconfig` for your local cluster and run with `KUBECONFIG=/path/to/kubeconfig.yml bash migrate.sh`. The script is idempotent and can be run multiple times safely if you want to validate just one at a time. **Notes:** - The [feature flag](https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-references/feature-flags) `provisioningprebootstrap` must be enabled after updating to one of the patched versions. This feature flag is also mandatory when installing a new cluster. - **Rancher 2.7 release line is not receiving a backport security patch for this vulnerability.** For users running Rancher 2.7 with vSphere provisioning and that are concerned with this security issue, the recommendation is to update Rancher to one of the patched versions by following the standard update procedure based on the 2.7 version that is being used. Refer to the release notes for the proper update process for [2.8.9](https://github.com/rancher/rancher/releases/tag/v2.8.9) and [2.9.3](https://github.com/rancher/rancher/releases/tag/v2.9.3). ### Workarounds Besides only granting access to Rancher to trusted users and not allowing direct access to untrusted users to the clusters' infrastructure, there is no direct workaround for this security issue, except updating Rancher to one of the patched versions. ### References If you have any questions or comments about this advisory: - Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries. - Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).

Read the publisher's advisory

osv · GO-2024-3223

Published

Exposure of vSphere's CPI and CSI credentials in Rancher in github.com/rancher/rancher. NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions. (If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.) The additional affected modules and versions are: github.com/rancher/rancher from v2.7.0 before v2.8.9, from v2.9.0 before v2.9.3.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2022-45157

Published

github.com/rancher/rancher

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "packageName": "github.com/rancher/rancher",
                    "product": "rancher",
                    "vendor": "SUSE",
                    "versions": [
                        {
                            "lessThan": "2.9.3",
                            "status": "affected",
                            "version": "2.9.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "2.8.9",
                            "status": "affected",
                            "version": "2.7.0",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-3170

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 13, 2024, 1:39:10 PM

dateUpdated: Nov 13, 2024, 2:39:15 PM

4 related source bulletins · separate from aliases

openSUSE-SU-2024:0350-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-0132 · CVE-2024-0133 · CVE-2024-10005 · CVE-2024-10006 · CVE-2024-10086 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-10452 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-39720 · CVE-2024-46872 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47401 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50052 · CVE-2024-50312 · CVE-2024-50354 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8185 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

openSUSE-SU-2024:14447-1: govulncheck-vulndb-0.0.20241030T212825-1.1 on GA media

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

SUSE-SU-2024:3911-1: Security update for govulncheck-vulndb

CVE-2022-45157 · CVE-2023-22644 · CVE-2023-32197 · CVE-2024-10214 · CVE-2024-10241 · CVE-2024-22030 · CVE-2024-22036 · CVE-2024-33662 · CVE-2024-36814 · CVE-2024-38365 · CVE-2024-39223 · CVE-2024-47003 · CVE-2024-47067 · CVE-2024-47182 · CVE-2024-47534 · CVE-2024-47616 · CVE-2024-47825 · CVE-2024-47827 · CVE-2024-47832 · CVE-2024-47877 · CVE-2024-48909 · CVE-2024-48921 · CVE-2024-49380 · CVE-2024-49381 · CVE-2024-49753 · CVE-2024-49757 · CVE-2024-50312 · CVE-2024-7558 · CVE-2024-7594 · CVE-2024-8037 · CVE-2024-8038 · CVE-2024-8901 · CVE-2024-8975 · CVE-2024-8996 · CVE-2024-9180 · CVE-2024-9264 · CVE-2024-9312 · CVE-2024-9313 · CVE-2024-9341 · CVE-2024-9355 · CVE-2024-9407 · CVE-2024-9486 · CVE-2024-9594 · CVE-2024-9675

WID-SEC-W-2024-3273: Rancher: Mehrere Schwachstellen

CVE-2022-45157 · CVE-2023-32197 · CVE-2024-22036

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2022-45157

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-522

Original publisher date fields

published: 2024-11-13T14:15:14.990

lastModified: 2026-06-17T05:09:29.793

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-xj7w-r753-vj8v

Published

github.com/rancher/rancher

Go

SEMVER · introduced 2.9.0 → fixed 2.9.3

github.com/rancher/rancher

Go

SEMVER · introduced 2.7.0 → fixed 2.8.9

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-3223

Published

github.com/rancher/rancher

Go

SEMVER · introduced 0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current