Client Spoofing within the Keycloak Device Authorisation Grant
Under certain pre-conditions the vulnerability allows an attacker to spoof parts of the device flow and use a device_code to retrieve an access token for other OAuth clients.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-2585US | high8.1 | — | ||
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 req… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2023:3883WEB
- https://access.redhat.com/errata/RHSA-2023:3884WEB
- https://access.redhat.com/errata/RHSA-2023:3885WEB
- https://access.redhat.com/errata/RHSA-2023:3888WEB
- https://access.redhat.com/errata/RHSA-2023:3892WEB
- https://access.redhat.com/security/cve/CVE-2023-2585WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2196335WEB
- https://github.com/keycloak/keycloakPACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan