Continued resource access after role removal
Published Jan 28, 2021 · Updated Aug 4, 2024
Incorrect authorization in Red Hat build of Keycloak before 13.0.0 allows remote authenticated users to retain access after role removal. Public records do not identify the component that fails to apply updated role mappings when issuing a token after the prior token expires. Exploitation requires a valid account whose role is revoked, and the stale authorization preserves access to resources protected by that role.
Summary
What happened
Incorrect authorization in Red Hat build of Keycloak before 13.0.0 allows remote authenticated users to retain access after role removal. Public records do not identify the component that fails to apply updated role mappings when issuing a token after the prior token expires. Exploitation requires a valid account whose role is revoked, and the stale authorization preserves access to resources protected by that role.
The record
- CVE
- CVE-2020-1725
- Published
- Jan 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=keycloak 13.0.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo