Keycloak vulnerable to session takeover with OIDC offline refreshtokens
An issue was discovered in Keycloak when using a client with the `offline_access` scope. Reuse of session ids across root and user authentication sessions and a lack of root session validation enabled attackers to resolve a user session attached to a different previously authenticated user. This issue most affects users of shared computers. Suppose a user logs out of their account (without clearing their cookies) in a mobile app or similar client that includes the `offline_access` scope, and another user authenticates to the application. In that case, it will share the same root session id, and when utilizing the refresh token, they will be issued a token for the original user.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-3916US | medium6.8 | — | ||
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 sess… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2022:8961WEB
- https://access.redhat.com/errata/RHSA-2022:8962WEB
- https://access.redhat.com/errata/RHSA-2022:8963WEB
- https://access.redhat.com/errata/RHSA-2022:8964WEB
- https://access.redhat.com/errata/RHSA-2022:8965WEB
- https://access.redhat.com/errata/RHSA-2023:1043WEB
- https://access.redhat.com/errata/RHSA-2023:1044WEB
- https://access.redhat.com/errata/RHSA-2023:1045WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan