CVE-2023-0657
Raw vector
CVSS:3.1/AV:A/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:NSummary
CVE-2023-0657 is a low-severity Improper Check for Dropped Privileges (CWE-273) vulnerability. Its CVSS base score is 3.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Access Token Manipulation (T1134); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-1142
Vulnerability Data
A flaw was found in Keycloak. This issue occurs due to improperly enforcing token types when validating signatures locally. This could allow an authenticated attacker to exchange a logout token for an access token and possibly gain access to data…
more
outside of enforced permissions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Employing least privilege requires that privilege-dropping operations succeed and are verified before continuing.
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 activities (code review, static analysis, testing) catch missing or incorrect privilege-drop checks, but eliminating only this one flaw covers only a fraction of the control's broader intent.
Least-privilege policy and enforcement directly motivate privilege-dropping code, yet the control does not address implementation-level verification of the drop.
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.
Security testing can detect failed privilege drops, yet the control does not require such checks as part of its core intent.
Control of privileged utility programs includes ensuring privilege-dropping operations are verified before use.
Privileged access rights policy requires verification that privilege changes succeed, directly addressing failed privilege drops.
Secure coding practices can prevent missing privilege-drop checks, but the control itself does not mandate verification of privilege changes.