Sssd: sssd: access control bypass via improper ldap shadow expiration check
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions |
|---|---|---|---|
| Red Hat | Red Hat Enterprise Linux 10 | affected | — |
| Red Hat | Red Hat Enterprise Linux 6 | unknown | — |
| Red Hat | Red Hat Enterprise Linux 7 | affected | — |
| Red Hat | Red Hat Enterprise Linux 8 | affected | — |
| Red Hat | Red Hat Enterprise Linux 9 | affected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | affected | — |
| Red Hat | Red Hat OpenShift Container Platform 4 | affected | — |
| Red Hat | Red Hat OpenShift Container Platform 5 | affected | — |
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Redhat | Enterprise Linux |
|
||||||||
| Redhat | Openshift Container Platform |
|
||||||||
| Sssd | Sssd |
|
Vendor Workaround
Until a fix is available, deployments using SSSD's LDAP shadow-based expiration (access_provider = ldap with ldap_access_order including expire and ldap_account_expire_policy = shadow) should not rely on shadowExpire=0 to expire accounts. Set the shadowExpire attribute to a positive past day value so that SSSD correctly treats the account as expired, or enforce account disablement or expiration through directory-side controls that do not depend solely on this client-side SSSD check. If SSSD has cached the affected account's attributes, invalidate the cached entry (for example with sss_cache -u <username>) or restart the sssd service so the updated directory values take effect; note that restarting the service or clearing cached data can briefly interrupt active authentication sessions on the host.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.235% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat rhel Els
|
|
| CPEs | cpe:/o:redhat:enterprise_linux:6 cpe:/o:redhat:enterprise_linux:7 cpe:/o:redhat:enterprise_linux:8 cpe:/o:redhat:enterprise_linux:9 |
cpe:/a:redhat:enterprise_linux:10 cpe:/a:redhat:enterprise_linux:8 cpe:/a:redhat:enterprise_linux:9 cpe:/a:redhat:openshift:5 cpe:/o:redhat:rhel_els:6 cpe:/o:redhat:rhel_els:7 |
| Vendors & Products |
Redhat rhel Els
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat openshift Container Platform
Sssd Sssd sssd |
|
| Vendors & Products |
Redhat openshift Container Platform
Sssd Sssd sssd |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in SSSD. When configured to enforce account expiration using LDAP (Lightweight Directory Access Protocol) shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass access controls and authenticate to the system. This allows unauthorized access to persist after the account was intended to be deactivated. | |
| Title | Sssd: sssd: access control bypass via improper ldap shadow expiration check | |
| First Time appeared |
Redhat
Redhat enterprise Linux Redhat openshift |
|
| Weaknesses | CWE-193 | |
| CPEs | cpe:/a:redhat:openshift:4 cpe:/o:redhat:enterprise_linux:10 cpe:/o:redhat:enterprise_linux:6 cpe:/o:redhat:enterprise_linux:7 cpe:/o:redhat:enterprise_linux:8 cpe:/o:redhat:enterprise_linux:9 |
|
| Vendors & Products |
Redhat
Redhat enterprise Linux Redhat openshift |
|
| References |
| |
| Metrics |
cvssV3_1
|