KeycloakApplication · Redhat
CVE-2020-1725
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 before version 13.0.0. In some scenarios a user still has access to a resource after changing the role mappings in Keycloak and after expiration of the previous access token.
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 before version 13.0.0 contains a flaw where user access to resources persists even after role mappings are changed and the previous access token expires. This suggests a caching or session state issue where the authorization decision is not properly re-evaluated when role mappings are modified.
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
< 13.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 the installed Keycloak versionCheck the version file in the Keycloak installation directory, or query the /health/ready endpoint, or run: 'keycloak/bin/kc.sh --version' from the server rootAffected if The installed version is any version before 13.0.0 (e.g., 12.x, 11.x, 10.x)
-
Locate the cache configuration fileFind the infinispan cache configuration file (usually in standalone/configuration/standalone.xml or standalone-ha.xml under the <cache-container> and <replicated-cache> elements for sessions)Affected if The default Infinispan cache configuration is in use without any custom invalidation settings for session or authorization caches
-
Inspect the session cache eviction settingsIn the cache configuration file, look for the 'session-cache' or 'sessions' cache definition and check for <expiration> settings and eviction configurationAffected if The session cache has no time-based expiration or the eviction settings are configured such that old role mappings may be retained in cache after role changes
-
Check for authentication session configurationLook for 'authenticationSessionCache' or 'userSessionCache' entries in the Infinispan cache configurationAffected if The user session cache is configured with long-lived entries that do not synchronize with role mapping changes in the underlying user storage
-
Verify token validity and refresh behaviorTest by obtaining an access token, changing the user's role mappings in the Keycloak admin console, waiting for the token to expire, then requesting a new token to see if old access persistsAffected if After role mappings are modified and the original token expires, a newly issued token still grants access based on the old (revoked) role mappings
You are affected if your Keycloak version is below 13.0.0 and users can still access resources with old roles after those roles have been removed and their tokens have expired.
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 data13.0.0
Upgrade Keycloak to version 13.0.0 or later to resolve the role mapping synchronization issue.
Fix this in Keycloak
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1725 — 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-1725 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