Identity Services EngineApplication · Cisco
CVE-2023-20030
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 · uneditedA vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to access sensitive information, conduct a server-side request forgery (SSRF) attack through an affected device, or negatively impact the responsiveness of the web-based management interface itself. This vulnerability is due to improper handling of XML External Entity (XXE) entries when parsing certain XML files. An attacker could exploit this vulnerability by uploading a crafted XML file that contains references to external entities. A successful exploit could allow the attacker to retrieve files from the local system, resulting in the disclosure of confidential information. A successful exploit could also cause the web application to perform arbitrary HTTP requests on behalf of the attacker or consume memory resources to reduce the availability of the web-based management interface. To successfully exploit this vulnerability, an attacker would need valid Super Admin or Policy Admin credentials.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in Cisco Identity Services Engine's web-based management interface. Attackers with Super Admin or Policy Admin credentials can upload crafted XML files containing external entity references to: (1) read local files from the server, (2) perform SSRF attacks making arbitrary HTTP requests, or (3) cause DoS through memory consumption.
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.2= 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L
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.
-
Determine Cisco ISE versionLog into the Cisco ISE admin CLI and run 'show version' or check the web UI dashboard for the software versionAffected if The installed version is 3.2 or any version lower than 3.2 (for example, 3.1, 3.0, 2.x releases)
-
Confirm web-based management interface is enabledVerify that the ISE web administration portal is accessible on ports 443 or 80, or check via CLI with 'show running-config | include http'Affected if The web management interface is active and the Cisco ISE version is vulnerable (3.2 or below)
-
Identify Super Admin or Policy Admin accountsIn the ISE web UI, navigate to Administration > Identity Management > Identities > Users, or run 'show running-config | include user' via CLI to list administrative accountsAffected if Super Admin or Policy Admin user accounts exist in the system (these are the roles required to exploit the vulnerability)
-
Review admin activity logs for XML file uploadsIn the ISE web UI, go to Operations > RADIUS > Reports or use the Live Logs feature to search for XML file upload events, or check log files for XXE patterns such as '<!ENTITY' or 'SYSTEM' in uploaded contentAffected if XML file uploads originating from admin sessions appear in the logs, indicating the exploitable feature is being used
Your environment is affected if Cisco ISE version 3.2 or lower is running, the web management interface is enabled, and privileged admin accounts (Super Admin or Policy Admin) exist in the system.
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.
dbcve · scoped3.2
Apply the Cisco ISE software update/patch when available. Until then, strictly limit admin credentials and monitor for unusual XML upload activity or unexpected outbound HTTP requests.
Cisco ISE 3.3 or later
- 1. Verify current Cisco ISE version by navigating to the Administration > System > Settings > System Configuration > About page in the web UI
- 2. Obtain valid Super Admin or Policy Admin credentials (required for exploitation)
- 3. Contact Cisco TAC or access the Cisco ISE software download page to obtain version 3.3 or later
- 4. Review Cisco ISE upgrade guide for proper upgrade procedure including backup recommendations
- 5. Perform a full backup of the ISE configuration before upgrading
- 6. Schedule maintenance window as upgrade will require system downtime
- 7. Upgrade to Cisco ISE version 3.3 or the latest stable release
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Identity Services Engine
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing8.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 $5,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20030 — 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-20030 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