Identity Services EngineApplication · Cisco
CVE-2023-20171
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 · uneditedMultiple 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 information about these vulnerabilities, see the Details section of this advisory.
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 confidenceMultiple vulnerabilities in Cisco Identity Services Engine allow an authenticated attacker to delete or read arbitrary files on the underlying operating system. The vulnerabilities stem from improper input validation in the ISE web interface, likely involving path traversal flaws that permit directory traversal outside of intended boundaries. An attacker with valid device credentials can exploit these to access or delete sensitive system files.
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
= 3.1= 3.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco ISE is installedLog into the ISE CLI or access the web administration interface and retrieve the software version. On the CLI, use the command 'show version' or 'show application' to identify the installed ISE version.Affected if The system is running Cisco Identity Services Engine version 3.1 or 3.2 exactly.
-
Verify the exact ISE version numberReview the version output from 'show version' or the web interface dashboard. Look for the full version string such as 3.1.0, 3.1.1, 3.2.0, etc.Affected if The installed version is 3.1.x or 3.2.x (any patch release within these major versions).
-
Confirm web interface is accessibleAttempt to access the ISE admin web portal at the configured IP/hostname on port 443 (HTTPS). Verify the service is running via CLI command 'show application status ise' to check if the web portal is active.Affected if The ISE web administration interface is accessible and operational.
-
Check for existing administrative accountsReview the ISE user database via the web interface under Administration > Identity Management > Identities > Users, or use the CLI command 'show running-config | include user' to list configured administrative accounts.Affected if At least one valid administrative or operator account exists in the ISE system.
A system is affected if it runs Cisco Identity Services Engine version 3.1 or 3.2, has the web interface enabled, and has at least one valid user account configured, allowing an authenticated attacker to exploit path traversal for arbitrary file access or deletion.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Cisco-provided patches for CVE-2023-20171 per the official advisory; restrict administrative access to only necessary personnel and implement least-privilege controls; monitor for anomalous file access patterns.
Fix this in Identity Services Engine
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20171 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-20171 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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