CVE-2023-2585

Description

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.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score3.58.1N/A
Attack VectorNetworkNetworkN/A
Attack ComplexityLowLowN/A
Privileges RequiredHighNoneN/A
User InteractionRequiredRequiredN/A
ScopeUnchangedUnchangedN/A
ConfidentialityLowHighN/A
Integrity ImpactLowHighN/A
Availability ImpactNoneNoneN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N

NVD: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Red Hat CVSS v3 Score Explanation

In order to exploit this following conditions needs to be met

  • The victim needs to be tricked into granting consent with an user_code to which the attacker has knowledge of the device_code. (The "consent" OAuth client can be spoofed, which makes this, in my opinion, a valid attack scenario.)
  • An attacker can only retrieve access tokens to which the victim previously granted consent.
  • All affected OAuth clients need to have the OAuth 2.0 Device Authorization Grant enabled. CVSS has been scored accordingly

Understanding the Weakness (CWE)

CWE-358

Access Control

Technical Impact: Bypass Protection Mechanism

Frequently Asked Questions

Not sure what something means? Check out our Security Glossary.

Want to get errata notifications? Sign up here.