A flaw was found in hawtio-operator. When deploying Hawtio in cluster mode, the operator creates a cluster-scoped OAuthClient with automatic grant approval (GrantMethod: auto) and no client secret (public client). The redirect URIs are derived from the operator-created Route, whose hostname is tenant-controlled via the Hawtio CR spec.routeHostName field. A malicious tenant can register an arbitrary hostname as a valid OAuth redirect target and, because grants are auto-approved, obtain OpenShift access tokens of any cluster user who visits the crafted authorization URL without any consent prompt.
Administrators can mitigate this issue by manually patching the OAuthClient resource created by the hawtio-operator to set grantMethod to 'prompt' instead of 'auto', and by adding a client secret. This forces explicit user consent for each OAuth authorization request and prevents unauthorized token acquisition. Monitor OpenShift OAuth server audit logs for unexpected authorization grants to the hawtio OAuthClient.