Identity Services EngineApplication · Cisco

CVE-2017-6734

MEDIUM · 5.4 CVSS v3.0 Published 2017-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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) Software could allow an authenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web interface of an affected device, related to the Guest Portal. More Information: CSCvd74794. Known Affected Releases: 1.3(0.909) 2.1(0.800).

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's Guest Portal web interface. An authenticated, remote attacker can inject malicious JavaScript code that executes in the browsers of other users viewing the Guest Portal, potentially allowing session hijacking or credential theft.

MitigationApply the Cisco patch referenced in CSCvd74794 or upgrade to a fixed release beyond 2.1(0.800). Refer to official Cisco security advisories for the complete list of fixed versions.

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:= 1.3\(0.722\)= 1.3\(0.876\)= 1.3\(0.909\)= 1.3\(106.146\)= 1.3\(120.135\)= 2.1\(0.474\)= 2.1\(0.800\)= 2.1\(102.101\)= 2.1_base

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.0/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. Identify Cisco ISE version
    Log into the Cisco ISE admin GUI and navigate to Administration > System > Licensing, or use the CLI command 'show version' to retrieve the installed software version.
    Affected if The installed version matches any of: 1.3(0.722), 1.3(0.876), 1.3(0.909), 1.3(106.146), 1.3(120.135), 2.1(0.474), 2.1(0.800), 2.1(102.101), or 2.1_base.
  2. Confirm Guest Portal is enabled
    In the Cisco ISE admin GUI, navigate to Guest Access > Portal Settings > Guest Portal to verify whether any Guest Portal type (Sponsor, Self-Registered, or Sponsored) is configured and enabled.
    Affected if Any Guest Portal is active, as the XSS flaw exists within the Guest Portal web interface.
  3. Verify web interface access
    Confirm that the Guest Portal is accessible to unauthenticated or externally-facing users by checking the portal configuration under Guest Access > Portal Settings and reviewing the allowed access settings.
    Affected if The Guest Portal web interface is reachable over the network, allowing the injected script to be delivered to victim browsers.

You are affected if your Cisco ISE version matches any of the listed affected versions AND the Guest Portal feature is enabled and accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco patch referenced in CSCvd74794 or upgrade to a fixed release beyond 2.1(0.800). Refer to official Cisco security advisories for the complete list of fixed versions.

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 help mitigating

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-2017-6734 — 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-2017-6734 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