CVE-2023-2585
Redhat Single Sign-On 7.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-2585 is a low-severity Improperly Implemented Security Check for Standard (CWE-358) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 3.5 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Steganography (T1001.002); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-1780
Vulnerability Data
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…
more
client or possible unauthorized access to an existing OAuth client.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.2.8
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Assessments identify and document improperly implemented security checks, allowing fixes that reduce exploitation of flawed checks.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct implementation of standardized security checks and algorithms.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Use of cryptography control depends on correct implementation of standardized cryptographic checks.
A.8.25 mandates security requirements, checkpoints, secure coding, testing (incl. code scans/pen tests) and developer capability in the SDLC, which reaches a minority slice of CWE-358 (incorrect implementation of a standardized security check) but leaves most instances (e.g. flawed protocol logic, spec misinterpretation, or non-coded design errors) unaddressed.
Application security requirements explicitly call for correct implementation of standardized security mechanisms.
A.8.27 mandates applying security-by-design principles (defense-in-depth, least privilege, fail securely, distrust external input, security-oriented design reviews) that reach some but not most instances of CWE-358, which is a narrow implementation error against a standardized check (e.g. protocol-level auth bypass, cert validation flaw) that can still arise in code even when the principles are followed.