Ce mail provient de l'extérieur, restons vigilants ===================================================================== CERT-Renater Note d'Information No. 2025/VULN732 _____________________________________________________________________ DATE : 24/10/2025 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running Rancher versions prior to 2.12.3, 2.11.7. ===================================================================== https://github.com/rancher/rancher/security/advisories/GHSA-j4vr-pcmw-hx59 https://github.com/rancher/rancher/security/advisories/GHSA-mw39-9qc2-f7mg _____________________________________________________________________ User retains access to clusters despite Global Role removal Moderate pdellamore published GHSA-j4vr-pcmw-hx59 Oct 23, 2025 Package github.com/rancher/rancher (Go) Affected versions >=2.12.0, <2.12.3 >=2.11.0, <2.11.7 >=2.10.0 >=2.9.0 Patched versions 2.12.3 2.11.7 Description Impact A vulnerability has been identified within Rancher Manager, where after removing a custom GlobalRole that gives administrative access or the corresponding binding, the user still retains access to clusters. This only affects custom Global Roles that: Have a * on * in * rule for resources Have a * on * rule for non-resource URLs For example apiVersion: management.cattle.io/v3 kind: GlobalRole metadata: name: custom-admin rules: - apiGroups: - '*' resources: - '*' verbs: - '*' - nonResourceURLs: - '*' verbs: - '*' Specifically: When a user is bound to a custom admin GlobalRole, a corresponding ClusterRoleBinding is created on all clusters that binds them to the cluster-admin ClusterRole. When such a GlobalRole or the GlobalRoleBinding (e.g., when the user is unassigned from this role in UI) is deleted, the ClusterRoleBinding that binds them to the cluster-admin ClusterRole stays behind. This issue allows a user to continue having access to clusters after they have been unassigned from the custom admin global role or the role has been deleted. Please consult the associated MITRE ATT&CK - Technique - Account Access Removal for further information about this category of attack. Patches This vulnerability is addressed by removing the corresponding ClusterRoleBindings whenever the admin GlobalRole or its GlobalRoleBindings are deleted. Previously orphaned ClusterRoleBindings are marked with the annotation authz.cluster.cattle.io/admin-globalrole-missing=true and should be deleted manually. Orphaned ClusterRoleBindings can be listed with: kubectl get clusterrolebinding -o jsonpath='{range .items[?(@.metadata.annotations.authz\.cluster\.cattle\.io/admin-globalrole-missing=="true")]}{.metadata.name}{"\n"}{end}' Patched versions of Rancher include releases v2.12.3, v2.11.7. Complications with the restricted admin functionality prevented the patches from being included in v2.10 and v2.9. Workarounds If the deployment can't be upgraded to a fixed version, users are advised to manually identify the orphaned ClusterRoleBindings and remove them. References If you have any questions or comments about this advisory: Contact 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. Severity Moderate 4.3/ 10 CVSS v3 base metrics Attack vector Network Attack complexity Low Privileges required High User interaction Required Scope Unchanged Confidentiality Low Integrity Low Availability Low CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L CVE ID CVE-2023-32199 Weaknesses No CWEs _____________________________________________________________________ Exposure of sensitive information through audit logs Moderate pdellamore published GHSA-mw39-9qc2-f7mg Oct 24, 2025 Package github.com/rancher/rancher (Go) Affected versions >=2.12.0, <2.12.3 >=2.11.0 >=2.10.0 >=2.9.0 Patched versions 2.12.3 Description Impact Note: The exploitation of this issue requires that the malicious user have access to Rancher’s audit log storage. A vulnerability has been identified in Rancher Manager, where sensitive information, including secret data, cluster import URLs, and registration tokens, is exposed to any entity with access to Rancher audit logs. This happens in two different ways: Secret Annotation Leakage: When creating Kubernetes Secrets using the stringData field, the cleartext value is embedded in the kubectl.kubernetes.io/last-applied-configuration annotation. This annotation is included in Rancher audit logs within both the request and response bodies, exposing secret material that should be redacted. Cluster Registration Token Leakage: During the import or creation of downstream clusters (Custom, Imported, or Harvester), Rancher audit logs record full cluster registration manifests and tokens, including: a. Non-expiring import URLs such as /v3/import/_c-m-xxxx.yaml. b. Full kubectl apply and curl commands containing registration tokens and CA checksums. c. Token values associated with cluster registration resources (clusterRegistrationToken). d. These tokens are valid until explicitly revoked and can be used to re-register nodes, granting unauthorized cluster access. An attacker or internal user who gains access to these logs could: Recover plaintext secret values from annotations. Use cluster registration tokens or import URLs to re-enroll agents or compromise downstream clusters. Access clusters that rely on these tokens for authentication, enabling lateral movement. Please consult the associated MITRE ATT&CK - Technique - Log Enumeration for further information about this category of attack. Patches This vulnerability is addressed by applying redaction to sensitive information that was leaking. Patched versions of Rancher include release v2.12.3. Workarounds If the deployment can't be upgraded to a fixed version, users are encouraged to create AuditPolicies to redact and filter some of those requests as described in our documentation. Also consider granting access to Rancher's logs only for trusted users. 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. Severity Moderate 4.3/ 10 CVSS v3 base metrics Attack vector Network Attack complexity Low Privileges required Low User interaction None Scope Unchanged Confidentiality Low Integrity None Availability None CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CVE ID CVE-2024-58269 Weaknesses No CWEs ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================