Red Hat Enterprise Linux 10
Sssd: sssd: idp authentication prefix comparison allows cross-user impersonation
A flaw was found in SSSD's IdP authentication provider. The eval_access_token_buf() function compares the OIDC subject identifier using strncmp() with the authenticated user's identifier length, performing a prefix comparison instead of an exact match. An attacker whose IdP identifier is a strict prefix of a target user's identifier can authenticate as the target user.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Fixed in 0:2.12.0-3.el10_2.2
Fixed in 0:2.13.1-3.el10_3
Mitigation
Upgrade Red Hat Enterprise Linux 10 to 0:2.12.0-3.el10_2.2 or later.
Upgrade Red Hat Enterprise Linux 10 to 0:2.13.1-3.el10_3 or later.
Workaround
Deployments not using the IdP authentication provider (idp_type = keycloak) are not affected. For affected deployments: (1) If using Keycloak LDAP federation, switching to Import Users: enabled mode causes Keycloak to assign random UUIDs as sub claims, making prefix collisions astronomically unlikely. (2) Restrict PAM login to specific users via simple_allow_users or access_provider = simple. (3) Disable Keycloak self-registration to prevent attackers from creating accounts with chosen prefix usernames.
References
- Vendor advisory access.redhat.com/errata/RHSA-2026:77534
- Vendor advisory access.redhat.com/errata/RHSA-2026:98559
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.