Session persistence via failed SAML backchannel logout
Published Apr 1, 2022 · Updated Aug 3, 2024
Insufficient session expiration in Red Hat Single Sign-On 7.4.7 allows local users to retain access after SAML logout. Red Hat identifies the affected locus as backchannel logout but has not published the code-level operation that fails to terminate the session. The condition requires an external SAML identity provider configured with Attribute [Name] as its Principal Type, leaving the authenticated session usable after logout.
Summary
What happened
Insufficient session expiration in Red Hat Single Sign-On 7.4.7 allows local users to retain access after SAML logout. Red Hat identifies the affected locus as backchannel logout but has not published the code-level operation that fails to terminate the session. The condition requires an external SAML identity provider configured with Attribute [Name] as its Principal Type, leaving the authenticated session usable after logout.
The record
- CVE
- CVE-2021-3461
- Published
- Apr 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat Single Sign-On
- Classifications
- CWE-613, T1078
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=rh-sso7-keycloak 9.0.13
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo