Description
A flaw was identified in the Docker v2 authentication endpoint of Keycloak, where tokens continue to be issued even after a Docker registry client has been administratively disabled. This means that turning the client “Enabled” setting to OFF does not fully prevent access. As a result, previously valid credentials can still be used to obtain authentication tokens. This weakens administrative controls and could allow unintended access to container registry resources.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.10-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-12 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-12 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.10
Default version status: unaffected
Red Hat Red Hat Build of Keycloak
Default version status: affected
Red Hat Red Hat Build of Keycloak
Default version status: affected
Red Hat Red Hat JBoss Enterprise Application Platform 8
Default version status: affected
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
Default version status: affected
Red Hat Red Hat Single Sign-On 7
Default version status: affected