GHSA-8P83-CPFG-FJ3G

Vulnerability from github – Published: 2025-04-01 14:19 – Updated: 2025-04-11 23:13
VLAI?
Summary
Rancher: Restricted Administrator can change Administrator's passwords
Details

Impact

A vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts.

A Restricted Administrator should be not allowed to change the password of more privileged users unless it contains the Manage Users permissions.

Rancher deployments where the Restricted Administrator role is not being used are not affected by this CVE. Please consult the associated MITRE ATT&CK - Technique - Abuse Elevation Control Mechanism for further information about this category of attack.

Patches

The fix introduces a few changes: 1. If the user has a manage-users verb, the user is allowed to edit/delete users. That way the Manage Users built in role will still be able to edit ALL users. 2. If the user doesn't have manage-users, just edit or delete, then there is a check to ensure that the User being edited only has rules equal to or less than the editor.

Patched versions include releases v2.8.14, v2.9.8, v2.10.4 and v2.11.0

Workarounds

Users are recommended to upgrade, as soon as possible, to a version of Rancher Manager that contains the fix. If users can't upgrade, the following are recommended: 1. Limit access to Rancher Restricted Admin only to trusted users. 2. Downgrade Restricted Administrators to custom roles with limited permissions.

Credits

This issue was identified and reported by Xavier Duthil from OVHcloud.

References

If you have any questions or comments about this advisory: - Reach out to the SUSE Rancher Security team for security related inquiries. - Open an issue in the Rancher repository. - Verify with our support matrix and product support lifecycle.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.8.0"
            },
            {
              "fixed": "2.8.14"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.9.0"
            },
            {
              "fixed": "2.9.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/rancher"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.10.0"
            },
            {
              "fixed": "2.10.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-23391"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-266"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-04-01T14:19:30Z",
    "nvd_published_at": "2025-04-11T11:15:42Z",
    "severity": "CRITICAL"
  },
  "details": "### Impact\nA vulnerability has been identified within Rancher where a Restricted Administrator can change the password of Administrators and take over their accounts. \n\nA Restricted Administrator should be not allowed to change the password of more privileged users unless it contains the Manage Users permissions.\n\nRancher deployments where the Restricted Administrator role is not being used are not affected by this CVE.\nPlease consult the associated  [MITRE ATT\u0026CK - Technique - Abuse Elevation Control Mechanism](https://attack.mitre.org/techniques/T1548/) for further information about this category of attack.\n\n### Patches\nThe fix introduces a few changes:\n1. If the user has a manage-users verb, the user is allowed to edit/delete users. That way the Manage Users built in role will still be able to edit ALL users.\n2. If the user doesn\u0027t have manage-users, just edit or delete, then there is a check to ensure that the User being edited only has rules equal to or less than the editor.\n\nPatched versions include releases `v2.8.14`, `v2.9.8`, `v2.10.4` and `v2.11.0`\n\n### Workarounds\nUsers are recommended to upgrade, as soon as possible, to a version of Rancher Manager that contains the fix.\nIf users can\u0027t upgrade, the following are recommended:\n1. Limit access to Rancher Restricted Admin only to trusted users.\n2. Downgrade Restricted Administrators to custom roles with limited permissions.\n\n### Credits\nThis issue was identified and reported by Xavier Duthil from OVHcloud.\n\n### References\nIf you have any questions or comments about this advisory:\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-8p83-cpfg-fj3g",
  "modified": "2025-04-11T23:13:29Z",
  "published": "2025-04-01T14:19:30Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/rancher/rancher/security/advisories/GHSA-8p83-cpfg-fj3g"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23391"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-23391"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/rancher/rancher"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Rancher: Restricted Administrator can change Administrator\u0027s passwords"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…