CVE-2025-54468

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Rancher ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial of Service herbeizuführen und Informationen auszuspähen.

### Impact A vulnerability has been identified within Rancher Manager whereby `Impersonate-Extra-*` headers are being sent to an external entity, for example `amazonaws.com`, via the `/meta/proxy` Rancher endpoint. These headers may contain identifiable and/or sensitive information e.g. email addresses. If the authentication provider is configured to have email or other sensitive and/or identifiable information as part of the username and principal ID then when a new cloud credential is being created in Rancher Manager this information is sent to an external entity such as `amazonaws.com`, in case of an AWS cloud credentials, in `Impersonate-Extra-Username` and/or `Impersonate-Extra-Principalid` headers. Please note that neither password, password hashes or Rancher’s related authentication tokens are leaked in those requests. The entities to which such information is sent to are limited by the whitelisted domains specified in `nodedrivers.management.cattle.io` objects. For example, the Amazon EC2 node driver contains the following whitelisted domains: - `iam.amazonaws.com` - `iam.us-gov.amazonaws.com` - `iam.%.amazonaws.com.cn` - `iam.global.api.aws` - `ec2.%.amazonaws.com` - `ec2.%.amazonaws.com.cn` - `ec2.%.api.aws` - `eks.%.amazonaws.com` - `eks.%.amazonaws.com.cn` - `eks.%.api.aws` - `kms.%.amazonaws.com` - `kms.%.amazonaws.com.cn` - `kms.%.api.aws` While the DigitalOcean driver contains the following whitelisted domain: - `api.digitalocean.com` ### Patches This vulnerability is addressed by filtering all `Impersonate-*` headers from the original request by the `/meta/proxy` endpoint. Patched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10, and v2.9.12. ### Workarounds There are no known workarounds for this issue. ### 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/).

Rancher sends sensitive information to external services through the `/meta/proxy` endpoint 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.9.0 before v2.9.12, from v2.10.0 before v2.10.10, from v2.11.0 before v2.11.6, from v2.12.0 before v2.12.2.