# CVE-2022-3916: Keycloak: session takeover with oidc offline refreshtokens

> Attackers can hijack user sessions via offline refresh tokens due to missing root session validation, leading to account takeover.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Sep 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-97g8-xfvw-q4hg

## What is CVE-2022-3916?

CVE-2022-3916 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 20 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-384 (Session Fixation)

## Which versions are affected by CVE-2022-3916?

2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-parent` | Maven | All versions | 20.0.2 |
| `org.keycloak:keycloak-parent` | Maven | All versions | 20.0.2 |

Products: Redhat Keycloak, Redhat Openshift Container Platform, Redhat Openshift Container Platform for Linuxone, Redhat Openshift Container Platform for Power, Redhat Openshift Container Platform Ibm Z Systems, Redhat Single Sign-On.

## How do I fix CVE-2022-3916?

Upgrade org.keycloak:keycloak-parent to 20.0.2 or later.

## Is CVE-2022-3916 being exploited?

There is no known exploitation of CVE-2022-3916 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Keycloak

- [CVE-2022-4361](https://insights.sbomify.com/CVE-2022-4361/): Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC (critical 10.0)
- [CVE-2022-1245](https://insights.sbomify.com/CVE-2022-1245/): Keycloak vulnerable to privilege escalation on Token Exchange feature (critical 9.8)
- [CVE-2021-20195](https://insights.sbomify.com/CVE-2021-20195/): keycloak Self Stored Cross-site Scripting vulnerability (critical 9.6)
- [CVE-2019-14910](https://insights.sbomify.com/CVE-2019-14910/): Keycloak Authentication Error (critical 9.3)
- [CVE-2019-14909](https://insights.sbomify.com/CVE-2019-14909/): Keycloak Authentication Error (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3916 and fix it if it is affected.

What it is: CVE-2022-3916 is a medium-severity authentication bypass vulnerability in Redhat Keycloak, published on 20 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3916 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 20.0.2
- org.keycloak:keycloak-parent (Maven): affected all versions; fixed in 20.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3916/ (Markdown: https://insights.sbomify.com/CVE-2022-3916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3916
- OSV: https://osv.dev/vulnerability/CVE-2022-3916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3916/
Summaries are generated and may contain mistakes; the official description above is the record.