KeycloakApplication · Redhat
CVE-2020-14366
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 vulnerability was found in keycloak, where path traversal using URL-encoded path segments in the request is possible because the resources endpoint applies a transformation of the url path to the file path. Only few specific folder hierarchies can be exposed by this flaw
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 confidenceA path traversal vulnerability in Keycloak's resources endpoint allows attackers to use URL-encoded path segments to access files outside the intended directory. The endpoint improperly transforms the URL path to a file path, exposing limited but sensitive folder hierarchies.
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
< 12.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installation and versionLocate the Keycloak installation directory. Check the version by examining the standalone.xml configuration file, startup logs, or the server's info endpoint (e.g., /auth/realms/master/server-info). Keycloak versions are typically displayed in the server startup banner.Affected if The installed version is any release prior to 12.0.0 (e.g., 11.x, 10.x, 9.x, etc.)
-
Confirm the resources endpoint is accessibleAttempt to access the Keycloak resources endpoint. In Keycloak versions prior to 12.0.0, this is typically located at /auth/resources/ or /resources/ serving static assets. Verify the endpoint responds to requests.Affected if The resources endpoint is exposed and responds to HTTP requests without authentication restrictions
-
Test for directory traversal in the resources endpointSend a crafted HTTP GET request to the resources endpoint using path traversal patterns. For example: GET /auth/resources/..%2F..%2F (URL-encoded) or /auth/resources/../ (standard). Inspect the response for signs of accessing files outside the intended resources directory.Affected if The server returns content from directories outside the intended resources folder, such as configuration files, log files, or system files accessible to the Keycloak process
You are affected if running any Keycloak version prior to 12.0.0 AND the resources endpoint is accessible and accepts path traversal patterns that expose files outside the intended directory.
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 data12.0.0
Apply the official Keycloak security patch for CVE-2020-14366; if immediate patching is not possible, implement input validation to reject directory traversal patterns in resource URLs.
Fix this in Keycloak
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-14366 — 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-14366 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