Identity Services EngineApplication · Cisco

CVE-2023-20021

MEDIUM · 6.7 CVSS v3.1 Published 2023-04-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple vulnerabilities in specific Cisco Identity Services Engine (ISE) CLI commands could allow an authenticated, local attacker to perform command injection attacks on the underlying operating system and elevate privileges to root. To exploit these vulnerabilities, an attacker must have valid Administrator privileges on the affected device. These vulnerabilities are due to insufficient validation of user-supplied input. An attacker could exploit these vulnerabilities by submitting a crafted CLI command. A successful exploit could allow the attacker to elevate privileges to root.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a command injection vulnerability in Cisco Identity Services Engine (ISE) CLI where insufficient input validation in specific CLI commands allows an authenticated Administrator to inject arbitrary OS commands and escalate privileges to root.

MitigationApply Cisco's security patches for CVE-2023-20021 to the affected ISE installation; restrict Administrator CLI access and monitor for suspicious command patterns until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Identity Services EngineApplication
Affected:= 3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco ISE installation
    Locate the ISE installation directory or check running services for 'Cisco ISE' or 'ise' processes on the system
    Affected if The system runs Cisco Identity Services Engine software
  2. Verify ISE version is 3.2
    Check the installed ISE version by logging into the ISE admin UI and navigating to Administration > System > About Cisco ISE, or run 'show version' in the ISE CLI
    Affected if The installed version is exactly 3.2 (no patch applied)
  3. Confirm CLI administrative access is enabled
    Check if the ISE CLI is accessible and Administrator accounts have CLI privileges via Administration > Administrators > Admin Users in the ISE UI, or by attempting CLI access with an admin account
    Affected if Administrator-level CLI access is available and configured
  4. Inspect for signs of command injection or privilege escalation
    Review ISE CLI command history (run 'show history' or check system logs), examine /opt directory for unexpected scripts, and check system logs for suspicious commands or unexpected root-level processes
    Affected if Unfamiliar commands in history, unexpected scripts in system directories, or unauthorized root-level processes are found

The environment is affected if Cisco ISE version 3.2 is running with CLI administrative access enabled, and either exploitation indicators are present or the system remains unpatched against CVE-2023-20021.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Cisco's security patches for CVE-2023-20021 to the affected ISE installation; restrict Administrator CLI access and monitor for suspicious command patterns until patched.

Fix this in Identity Services Engine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20021 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data