Mobile Application PlatformApplication · Redhat
CVE-2020-1723
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 Keycloak Gatekeeper (Louketo). The logout endpoint can be abused to redirect logged-in users to arbitrary web pages. Affected versions of Keycloak Gatekeeper (Louketo): 6.0.1, 7.0.0
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 Gatekeeper (Louketo) logout endpoint does not properly validate redirect URLs, allowing attackers to craft malicious links that redirect logged-in users to arbitrary external websites after logout. This open redirect vulnerability (CWE-601) with CVSS 6.1 could facilitate phishing attacks by exploiting user trust in the authenticated session.
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
Mobile Application PlatformApplication
= 4.0= 6.0.1= 7.0.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 Keycloak Gatekeeper installationLocate the Louketo/Keycloak Gatekeeper binary or service. Common locations: /opt/louketo, /usr/local/bin/, or check running processes for 'gatekeeper' or 'louketo'. On Kubernetes, check for deployments with these names.Affected if Keycloak Gatekeeper or Louketo proxy is deployed in the environment
-
Determine installed Gatekeeper versionRun 'gatekeeper --version' or 'louketo --version' on the binary, or check the container image tag if running in containers. Compare the version number against 6.0.1 and 7.0.0.Affected if The installed version is exactly 6.0.1 or exactly 7.0.0 (these are the affected versions)
-
Verify logout endpoint is configuredExamine the Gatekeeper configuration file (YAML or flags) for 'logout' endpoint settings. Check if 'redirect-url' or 'oauth' logout parameters are defined. Look for any 'url' or 'redirect' parameters in logout-related configuration.Affected if Logout endpoint is enabled and configured with redirect URL parameters
-
Inspect logout request handlingReview the Gatekeeper logs or network traffic when a logout request is made. Check if the logout endpoint accepts a 'redirect' or 'return_url' query parameter. Look for how the application handles the 'http://' or 'https://' prefix in redirect values.Affected if The logout endpoint accepts arbitrary URLs (absolute URLs with http/https schemes) as redirect targets
The environment is affected if Keycloak Gatekeeper/Louketo versions 6.0.1 or 7.0.0 are installed AND the logout endpoint is accessible and processes redirect parameters without strict validation.
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 URL validation on the logout endpoint to ensure redirect targets are relative paths or whitelisted domains; avoid allowing arbitrary or absolute URLs in redirect parameters.
Fix this in Mobile Application Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1723 — 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-2020-1723 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