CVE-2020-1725 Incorrect Authorization in keycloak
Users retain access to resources after role changes due to stale access tokens, allowing unauthorized access in Keycloak.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-1725?
CVE-2020-1725 is a medium-severity missing authorization vulnerability in Redhat Keycloak, published on 28 Jan 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
A 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.
Weakness: CWE-863
Which versions are affected by CVE-2020-1725?
2 open source packages ship an affected version, including org.keycloak:keycloak-parent. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.keycloak:keycloak-parent Maven | All versions | 13.0.0 |
org.keycloak:keycloak-parent Maven | All versions | 13.0.0 |
Products include Redhat Keycloak.
How do I fix CVE-2020-1725?
Upgrade org.keycloak:keycloak-parent to 13.0.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2020-1725 being exploited?
There is no known exploitation of CVE-2020-1725 in the wild and no public exploit code.
Other vulnerabilities in Redhat Keycloak
- CVE-2022-4361 Keycloak vulnerable to cross-site scripting when validating URI-schemes on SAML and OIDC
- CVE-2022-1245 Keycloak vulnerable to privilege escalation on Token Exchange feature
- CVE-2021-20195 keycloak Self Stored Cross-site Scripting vulnerability
- CVE-2019-14910 Keycloak Authentication Error
- CVE-2019-14909 Keycloak Authentication Error
Sources
Also known as GHSA-p225-pc2x-4jpm.