Keycloak Node.js AdapterApplication · Redhat
CVE-2022-2237
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 · uneditedA flaw was found in the Keycloak Node.js Adapter. This flaw allows an attacker to benefit from an Open Redirect vulnerability in the checkSso function.
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 · moderate confidenceThe Keycloak Node.js Adapter contains an Open Redirect vulnerability in the checkSso function. An attacker can craft a malicious URL that tricks the application into redirecting users to an arbitrary site, potentially leading to phishing or credential theft.
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
Keycloak Node.js AdapterApplication
all versions
Single Sign OnApplication
= 7.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 if Keycloak Node.js Adapter is installedRun 'npm list keycloak-connect' or check package.json for keycloak-connect or keycloak dependenciesAffected if The package is present in node_modules or package.json
-
Locate code using checkSso functionSearch codebase for 'checkSso' string in JavaScript/TypeScript files, particularly in authentication middleware or login flow handlersAffected if Code explicitly calls checkSso() method from Keycloak adapter
-
Inspect redirect URL handlingReview the code that handles redirects after checkSso completes - look for req.session['keycloak-token'] or similar token handling, and check if redirect URLs are validated against an allowlistAffected if Redirects occur without strict domain allowlist validation on the redirect target
-
Check application configuration for redirect validationReview keycloak.json or keycloak.js config files and any custom middleware that handles post-authentication redirectsAffected if No custom URL validation logic exists for redirect targets in the application
If Keycloak Node.js Adapter is installed and checkSso() is used in the authentication flow without custom allowlist-based URL validation, the application is vulnerable to open redirect attacks.
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.
From vendor dataImplement strict allowlist-based URL validation for redirect targets in the checkSso function, ensuring only trusted domains are permitted for redirects.
Fix this in Keycloak Node.js Adapter
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-2237 — 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-2237 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