Keycloak's device authorization grant does not correctly validate the device code and client ID. An attacker client could abuse the missing validation to spoof a client consent request and trick an authorization admin into granting consent to a malicious OAuth client or possible unauthorized access to an existing OAuth client.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| redhat | single_sign-on | - | - |
| redhat | openshift_container_platform | - | - |
| redhat | openshift_container_platform |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
10
Affected Products
14
References
redhat / single_sign-on
| - |
| - |
| redhat | openshift_container_platform_for_ibm_z | - | - |
| redhat | openshift_container_platform_for_ibm_z | - | - |
| redhat | openshift_container_platform_for_linuxone | - | - |
| redhat | openshift_container_platform_for_linuxone | - | - |
| redhat | openshift_container_platform_for_power | - | - |
| redhat | openshift_container_platform_for_power | - | - |
| redhat | single_sign-on | - | - |
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N
Exploitability
Impact