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.
References
Link | Resource |
---|---|
https://access.redhat.com/errata/RHSA-2023:3883 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2023:3884 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2023:3885 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2023:3888 | Vendor Advisory |
https://access.redhat.com/errata/RHSA-2023:3892 | Vendor Advisory |
https://access.redhat.com/security/cve/CVE-2023-2585 | Vendor Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=2196335 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
AND |
|
Configuration 2 (hide)
AND |
|
Configuration 3 (hide)
|
History
No history.
Information
Published : 2023-12-21 10:15
Updated : 2024-01-02 18:28
NVD link : CVE-2023-2585
Mitre link : CVE-2023-2585
CVE.ORG link : CVE-2023-2585
JSON object : View
Products Affected
redhat
- openshift_container_platform_for_ibm_z
- single_sign-on
- openshift_container_platform_for_linuxone
- enterprise_linux
- openshift_container_platform
- openshift_container_platform_for_power
CWE