Identity Services EngineApplication · Cisco
CVE-2019-12637
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 the web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the web-based management interface. The vulnerabilities are due to insufficient validation of user-supplied input that is processed by the web-based management interface. An attacker could exploit these vulnerabilities by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or access sensitive, browser-based information.
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 · high confidenceMultiple cross-site scripting (XSS) vulnerabilities exist in the web-based management interface of Cisco Identity Services Engine (ISE) due to insufficient validation of user-supplied input. An authenticated attacker can exploit these by tricking a user into clicking a crafted link, enabling execution of arbitrary script code in the context of the interface or access to sensitive browser-based information.
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
<= 2.3= 2.3.0.298= 2.4.0.357CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 installedAccess the administrative console or use command line (show version) on the ISE appliance to identify if Cisco Identity Services Engine is runningAffected if The product is Cisco ISE and the web-based management interface is accessible
-
Check installed Cisco ISE versionLog into the ISE admin web interface and navigate to Administration > System > Settings > System Time and Info, or use the CLI command 'show version' to retrieve the exact version numberAffected if The version is 2.3.0.298, 2.4.0.357, or any version 2.3 and below (versions <= 2.3)
-
Verify web-based management interface is enabledConfirm the ISE admin web interface (typically port 443 or 8443) is accessible and operational by attempting to reach the login pageAffected if The web management interface is exposed and reachable
-
Identify active authenticated sessionsIn the ISE admin console, check for active administrator sessions under Administration > System > Admin Access > Administrators or review recent authentication logsAffected if There are active administrator sessions or recent authentication activity, as the vulnerability requires an authenticated attacker to exploit
A user is affected if Cisco ISE is running with a version of 2.3.0.298, 2.4.0.357, or any version 2.3 and below, and the web-based management interface is accessible.
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 the vendor-supplied patches for Cisco ISE to address the input validation flaws. Users should be cautioned against clicking untrusted links until the patch is deployed.
Fix this in Identity Services Engine
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12637 — 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-2019-12637 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