CVE-2023-20106
Cisco Identity Services Engine 3.1 … 3.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2023-20106 is a medium-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Cisco Identity Services Engine. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-24285
Vulnerability Data
Multiple vulnerabilities in Cisco Identity Services Engine (ISE) could allow an authenticated attacker to delete or read arbitrary files on the underlying operating system. To exploit these vulnerabilities, an attacker must have valid credentials on an affected device. For more…
more
information about these vulnerabilities, see the Details section of this advisory.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V10.7.1V2.2.2V8.3.1V10.4.1
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.
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.
Secure architecture principles discourage client-side trust but do not directly address this weakness.
Security testing can detect client-side enforcement but is not the primary mitigation.
Information access restriction is undermined when the client is trusted to enforce it.
Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.
Application security requirements explicitly call for server-side enforcement of security mechanisms.
Secure coding standards require server-side checks and reject client-only enforcement.