Identity Services EngineApplication · Cisco

CVE-2019-12638

MEDIUM · 5.4 CVSS v3.1 Published 2019-10-16
Fix available
A fix is available. Upgrade to after 2.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A vulnerability 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 vulnerability is due to insufficient validation of user-supplied input that is processed by the web-based management interface. An attacker could exploit this vulnerability 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 confidence

Cross-site scripting (XSS) vulnerability in Cisco Identity Services Engine web-based management interface. An authenticated attacker can inject malicious scripts through insufficiently validated user input, which then executes in the context of other users' browser sessions when they view the crafted content.

MitigationApply the Cisco security patch for CVE-2019-12638. As a defense-in-depth measure, implement Content Security Policy (CSP) headers and ensure proper input validation is enforced on the ISE management interface.

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:<= 2.2.0= 2.3= 2.3\(0.298\)= 2.4= 2.4\(0.357\)= 2.6\(0.156\)= 2.7\(0.999\)

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
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 checks

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

  1. Determine Cisco ISE version
    Log into the Cisco ISE admin CLI and run the command 'show version' or access the Administration > System > Settings > Product Version in the web UI to identify the installed version.
    Affected if The installed version matches <= 2.2.0, 2.3, 2.3(0.298), 2.4, 2.4(0.357), 2.6(0.156), or 2.7(0.999).
  2. Verify web-based management interface is enabled
    Confirm the Cisco ISE admin web interface is accessible by attempting to reach the management portal URL (typically https://<ise-host>/admin/). Check if the service is running via CLI command 'show application status ise' or equivalent.
    Affected if The web-based management interface is active and reachable.
  3. Confirm administrative access exists
    Review user accounts with administrative privileges in Cisco ISE (Administration > Identity Management > Identities > Users). The vulnerability requires an authenticated attacker, so any admin or privileged user account could be leveraged.
    Affected if At least one active administrative or privileged user account exists in the ISE system.

You are affected if your Cisco ISE version is one of the listed affected versions AND the web-based management interface is accessible with authenticated user accounts.

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
Upgrade available Upgrade to a release after 2.2.0
Interim mitigation

Apply the Cisco security patch for CVE-2019-12638. As a defense-in-depth measure, implement Content Security Policy (CSP) headers and ensure proper input validation is enforced on the ISE management interface.

Fix this in Identity Services Engine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12638 — 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-2019-12638 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