KeycloakApplication · Redhat
CVE-2017-12160
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 · uneditedIt was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.
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 confidenceIn Keycloak's OAuth implementation, refresh tokens remain valid and can be exchanged for new access tokens even after a user's permissions have been revoked. An attacker who has compromised a resource with valid tokens can continue obtaining fresh token pairs indefinitely, maintaining unauthorized access despite administrative revocation attempts.
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
all versionsCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 deploymentSearch for Keycloak services, containers, or installations in your environment. Look for keycloak-related processes, Docker containers, or web applications running on common Keycloak ports (8080, 8443). Check your infrastructure configuration files for Keycloak references.Affected if Keycloak is deployed in your environment - all versions are affected by this vulnerability
-
Locate Keycloak configuration filesFind the standalone.xml, standalone-ha.xml, or keycloak.json configuration files typically located in the Keycloak server's conf directory. These files control token settings and realm configurations.Affected if Configuration files exist - this confirms a Keycloak installation to inspect further
-
Check for custom token revocation implementationInspect the Keycloak server's configuration and any custom extensions or plugins for refresh token revocation logic. Look for implementations that handle token revocation on permission changes, particularly in the realm or server configuration.Affected if No custom refresh token revocation mechanism is found - the vulnerability exists
-
Review token settings in realm configurationExamine the realm settings in Keycloak's admin console or configuration for access token and refresh token lifespans, and verify if there are explicit revocation check configurations. Search for settings related to offline access or token persistence.Affected if Refresh tokens are configured without explicit revocation-on-permission-change checks
If Keycloak is deployed without custom refresh token revocation logic that invalidates tokens when permissions are revoked, the environment is affected by this CVE.
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 dataUpgrade Keycloak to a version that properly invalidates refresh tokens on permission revocation, or implement custom token revocation logic to ensure refresh tokens are invalidated when permissions are withdrawn.
Fix this in Keycloak
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12160 — 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-2017-12160 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