Keycloak: session takeover with oidc offline refreshtokens
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 20.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in the offline_access scope in Keycloak. This issue would affect users of shared computers more (especially if cookies are not cleared), due to a lack of root session validation, and the reuse of session ids across root and user authentication sessions. This enables an attacker to resolve a user session attached to a previously authenticated user; when utilizing the refresh token, they will be issued a token for the original user.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- keycloak
Version range not reported
- keycloak
Version range not reported
- rh-sso7-keycloak
Version range not reported
- rh-sso7-keycloak
Version range not reported
- rh-sso7-keycloak
Version range not reported
- rh-sso7-keycloak
Version range not reported
- rh-sso7-keycloak
Version range not reported
- rh-sso7-keycloak
Version range not reported
- rh-sso-7/sso76-openshift-rhel8
Version range not reported
- rh-sso-7/sso76-openshift-rhel8
Version range not reported
- org.keycloak:keycloak-parentMaven
fixed in 20.0.2