Identity Services EngineApplication · Cisco

CVE-2019-12644

MEDIUM · 6.1 CVSS v3.0 Published 2019-09-05
Fix available
A fix is available. Upgrade to 2.6.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability exists because the web-based management interface of the affected device does not properly validate user-supplied input. An attacker could exploit this vulnerability by persuading a user to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in Cisco Identity Services Engine (ISE) web-based management interface. The interface fails to properly validate user-supplied input, allowing unauthenticated remote attackers to inject malicious scripts via crafted links. Successful exploitation enables arbitrary code execution in the context of the affected interface or access to sensitive browser-based information.

MitigationApply the Cisco ISE patch for CVE-2019-12644. Until patched, users should avoid clicking untrusted links to the management interface. Implement input validation and output encoding as defense-in-depth measures.

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.6.0= 2.7\(0.207\)

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 web interface and navigate to Administration > System > Settings > Product Version, or run 'show version' command via CLI
    Affected if The displayed version is below 2.6.0 or exactly 2.7(0.207)
  2. Verify web-based management interface is enabled
    Check if the ISE admin web interface is accessible by attempting to reach the login page at the configured admin URL (default ports 443 or 8080)
    Affected if The web management interface is exposed and the version falls within the affected range
  3. Confirm administrative access method
    Review network accessibility settings in ISE under Administration > Network Access > Network Device Definition to determine if the admin interface is reachable from untrusted networks
    Affected if The management interface is accessible from outside the trusted network and the version is vulnerable

A system is affected if it runs Cisco ISE versions below 2.6.0 or exactly version 2.7(0.207) and has the web-based management interface exposed.

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 2.6.0 or later
Fixed in 2.6.0
Interim mitigation

Apply the Cisco ISE patch for CVE-2019-12644. Until patched, users should avoid clicking untrusted links to the management interface. Implement input validation and output encoding as defense-in-depth measures.

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 the upgrade done

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-2019-12644 — 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-12644 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