dbcve.org
Identity Services EngineApplication · Cisco

CVE-2017-6733

MEDIUM · 6.1 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 →
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 application interface of the Cisco Identity Services Engine (ISE) portal could allow an unauthenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the web interface of an affected system. More Information: CSCvd87482. Known Affected Releases: 2.1(102.101) 2.2(0.283) 2.3(0.151).

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

A stored cross-site scripting (XSS) vulnerability in Cisco Identity Services Engine (ISE) web portal allows an unauthenticated remote attacker to inject malicious scripts into the web interface. This stored payload executes when legitimate users access the compromised portal content.

MitigationApply the vendor patch per CSCvd87482 or upgrade to a Cisco ISE release beyond 2.3(0.151). Until patched, restrict network access to the ISE portal and monitor for anomalous requests.

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.1\(102.101\)= 2.2\(0.283\)= 2.3\(0.151\)

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. Identify Cisco ISE version
    Log into the ISE CLI and run the command: show version | include Version. Alternatively, access the ISE web UI and navigate to Administration > System > Settings > System Configuration and view the version information.
    Affected if The installed version matches exactly 2.1(102.101), 2.2(0.283), or 2.3(0.151)
  2. Determine if guest portal is enabled
    In the ISE web UI, navigate to Administration > Portal Settings > Portals and check if any guest portals (Sponsor Portal, Guest Portal, or Hotspot Portal) are configured and enabled.
    Affected if Any ISE guest or sponsor portal is accessible and enabled on the network
  3. Review portal configuration for injected scripts
    In the ISE web UI, navigate to Guest > Portals and Templates. Inspect each portal configuration for any unexpected JavaScript tags, script elements, or suspicious content in fields such as banner messages, login page customizations, or redirect URLs.
    Affected if Malicious script tags or JavaScript code are found stored in any portal configuration fields
  4. Check authentication logs for XSS indicators
    In the ISE web UI, go to Operations > RADIUS > Live Logs or ISE Reports > Endpoints and Users. Search for unusual URL-encoded characters in username or sponsor fields that may indicate XSS injection attempts.
    Affected if Logs show repeated XSS payload patterns or unusual script-related strings in user input fields

You are affected if your Cisco ISE version is exactly 2.1(102.101), 2.2(0.283), or 2.3(0.151) AND the ISE guest/sponsor portal is accessible on your network.

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 vendor patch per CSCvd87482 or upgrade to a Cisco ISE release beyond 2.3(0.151). Until patched, restrict network access to the ISE portal and monitor for anomalous requests.

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

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-2017-6733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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