ghsa-mjcp-rj3c-36fr
Vulnerability from github
Published
2025-09-26 13:02
Modified
2025-10-02 15:11
Severity ?
4.7 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
Summary
Rancher sends sensitive information to external services through the `/meta/proxy` endpoint
Details

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:

Show details on source website

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.12.0"
            },
            {
              "fixed": "2.12.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.11.0"
            },
            {
              "fixed": "2.11.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.10.0"
            },
            {
              "fixed": "2.10.10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.9.0"
            },
            {
              "fixed": "2.9.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-54468"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-09-26T13:02:38Z",
    "nvd_published_at": "2025-10-02T10:15:39Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nA 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.\n\nIf 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\u2019s related authentication tokens are leaked in those requests.\n\nThe entities to which such information is sent to are limited by the whitelisted domains specified in `nodedrivers.management.cattle.io` objects. \n\nFor example, the Amazon EC2 node driver contains the following whitelisted domains:\n\n- `iam.amazonaws.com`\n- `iam.us-gov.amazonaws.com`\n- `iam.%.amazonaws.com.cn`\n- `iam.global.api.aws`\n- `ec2.%.amazonaws.com`\n- `ec2.%.amazonaws.com.cn`\n- `ec2.%.api.aws`\n- `eks.%.amazonaws.com`\n- `eks.%.amazonaws.com.cn`\n- `eks.%.api.aws`\n- `kms.%.amazonaws.com`\n- `kms.%.amazonaws.com.cn`\n- `kms.%.api.aws`\n\nWhile the DigitalOcean driver contains the following whitelisted domain:\n\n- `api.digitalocean.com`\n\n### Patches\n\nThis vulnerability is addressed by filtering all `Impersonate-*` headers from the original request by the `/meta/proxy` endpoint.\n\nPatched versions of Rancher include releases v2.12.2, v2.11.6, v2.10.10, and v2.9.12. \n\n### Workarounds\n\nThere are no known workarounds for this issue.\n\n### References\n\nIf you have any questions or comments about this advisory:\n\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- 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/).",
  "id": "GHSA-mjcp-rj3c-36fr",
  "modified": "2025-10-02T15:11:50Z",
  "published": "2025-09-26T13:02:38Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/rancher/rancher/security/advisories/GHSA-mjcp-rj3c-36fr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54468"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-54468"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/rancher/rancher"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Rancher sends sensitive information to external services through the `/meta/proxy` endpoint"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.