REDHAT-BUG-2509764: Medium severity Keycloak Keycloak vulnerability
A state-based policy bypass vulnerability was discovered in Keycloak's client policy engine. The flaw exists in the way the access-type condition evaluates UPDATE operations. Specifically, the condition checks the old client state instead of the proposed new state during an update. An attacker with low privileges, such as delegated client management permissions or a valid dynamic registration token, can exploit this by creating a public client and subsequently updating it to a confidential client. Because the policy engine still perceives the client as public during the update process, it fails to trigger the confidential-client policy profile. This allows the attacker to configure a confidential client with weak authentication (e.g., client-secret) even when the realm policy mandates stronger methods like client-jwt. Successful exploitation allows an attacker to persist non-compliant confidential clients, undermining realm-level security hardening.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2509764?
The severity of REDHAT-BUG-2509764 is classified as medium, with a risk score of 4.
What does the vulnerability REDHAT-BUG-2509764 affect?
REDHAT-BUG-2509764 affects Keycloak's client policy engine and the access-type condition during UPDATE operations.
How do I fix REDHAT-BUG-2509764?
To fix REDHAT-BUG-2509764, upgrade to the latest version of Keycloak where the vulnerability has been patched.
How does REDHAT-BUG-2509764 allow exploitation?
REDHAT-BUG-2509764 allows exploitation by an attacker who can manipulate the access-type condition due to the flawed evaluation of client states.
What is the nature of the vulnerability in REDHAT-BUG-2509764?
The nature of the vulnerability in REDHAT-BUG-2509764 is a state-based policy bypass in the Keycloak client policy engine.