# CVE-2022-3782: Keycloak vulnerable to path traversal via double URL encoding

> Attackers can bypass redirect validation via double URL encoding to access sensitive internal URLs in Keycloak instances using wildcard redirect URIs.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-g8q8-fggx-9r3q

## What is CVE-2022-3782?

CVE-2022-3782 is a critical path traversal vulnerability in Redhat Keycloak, published on 11 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

keycloak: path traversal via double URL encoding. A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. An attacker can use this flaw to construct a malicious request to bypass validation and access other URLs and potentially sensitive information within the domain or possibly conduct further attacks. This flaw affects any client that utilizes a wildcard in the Valid Redirect URIs field.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| 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.

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

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

## Is CVE-2022-3782 being exploited?

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

Public exploit code:

- https://github.com/shoucheng3/keycloak__keycloak_CVE-2022-3782_20-0-1 (github_poc): https://github.com/shoucheng3/keycloak__keycloak_CVE-2022-3782_20-0-1

## 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-3782 and fix it if it is affected.

What it is: CVE-2022-3782 is a critical path traversal vulnerability in Redhat Keycloak, published on 11 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3782 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-3782/ (Markdown: https://insights.sbomify.com/CVE-2022-3782/index.md)
```

## Sources

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

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