KeycloakApplication · Redhat
CVE-2022-3782
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedkeycloak: 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKeycloak fails to properly validate redirect URLs when double URL encoded, allowing attackers to bypass the Valid Redirect URI check. When clients use wildcards in their redirect URI configuration, malicious URLs can be crafted to pass validation and redirect users to attacker-controlled domains, potentially exposing sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
KeycloakApplication
= 20.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Keycloak versionCheck the Keycloak server version via the admin console (Server Info > Versions page), startup logs, or by querying the /realms/master endpointAffected if The installed version is exactly 20.0.2
-
Review client Valid Redirect URI configurationsIn the Keycloak admin console, navigate to each realm and examine client settings. Look specifically at the 'Valid Redirect URIs' field in each client configuration for wildcard patterns containing the * characterAffected if Any client has a Valid Redirect URI configured with wildcards (e.g., https://example.com/* or https://*.example.com)
-
Test double URL encoded redirect validation bypassAttempt to use a redirect URL with double URL encoded characters (e.g., containing %252F, %252E, or %252E%252F sequences) as the redirect target. Observe whether the validation passes when it should reject the malicious URLAffected if Double URL encoded redirect URLs bypass the Valid Redirect URI check and allow redirects to attacker-controlled domains
You are affected if running Keycloak version 20.0.2 AND have any client configured with wildcard Valid Redirect URIs that can be bypassed via double URL encoding
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedRemove wildcards from Valid Redirect URIs and use exact URL matches; apply Keycloak security patches; implement additional redirect URL validation layers.
Keycloak 21.x or later stable release
- 1. Identify all Keycloak instances currently running version 20.0.2 in your environment
- 2. Back up all Keycloak configurations, databases, and custom themes before upgrading
- 3. Download the latest stable Keycloak release (21.x or newer) from the official Keycloak website or your package manager
- 4. Stop the running Keycloak 20.0.2 service
- 5. Install the new Keycloak version following standard upgrade procedures
- 6. Review the Valid Redirect URIs configuration for all clients and remove any unnecessary wildcards
- 7. Start the upgraded Keycloak service
- 8. Test that authentication flows work correctly with legitimate redirect URIs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Keycloak
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data