Identity Services Engine SoftwareApplication · Cisco
CVE-2018-0339
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 · uneditedA vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web-based interface. The vulnerability is due to insufficient input validation of some parameters passed to the web-based management interface. An attacker could exploit this vulnerability by convincing a user of the interface to click a specific link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information. Cisco Bug IDs: CSCvf72309.
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 confidenceThis is a cross-site scripting (XSS) vulnerability in Cisco Identity Services Engine (ISE) web-based management interface. The vulnerability stems from insufficient input validation on certain parameters passed to the web interface, allowing an attacker to inject malicious script code. Successful exploitation requires tricking a user into clicking a crafted link, which can then execute arbitrary JavaScript in the victim's browser context or exfiltrate sensitive session 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 Engine SoftwareApplication
= 2.3\(0.298\)= 2.4\(0.126\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco ISE installationLocate the Cisco ISE appliance or container and confirm the web-based management interface is active by accessing the admin portal URL (typically https://<ise-host>/admin)Affected if The ISE web management interface is accessible and the system is reachable from network locations where untrusted users could send crafted links
-
Determine installed Cisco ISE versionLog into the ISE CLI or admin web interface and navigate to Administration > System > Settings > About Cisco ISE, or run 'show version' command in the CLI to retrieve the exact software version numberAffected if The installed version matches exactly 2.3(0.298) or 2.4(0.126)
-
Verify version falls within affected rangeCompare the retrieved version string from the previous step against the affected versions = 2.3(0.298) and = 2.4(0.126) - note that these are exact version matches onlyAffected if Running exactly version 2.3(0.298) or exactly version 2.4(0.126)
-
Assess network exposure of management interfaceReview firewall rules, access control lists, or ISE network settings to determine if the web management interface is exposed to the internet or untrusted internal networksAffected if The ISE admin portal is reachable from untrusted networks without proper filtering
A user is affected if their Cisco ISE runs exactly version 2.3(0.298) or 2.4(0.126) and the web-based management interface is network-accessible to attackers who could deliver crafted XSS links.
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 Cisco patch for CSCvf72309. Until patched, users should be cautioned against clicking untrusted links to the ISE management interface. Implement additional web application firewall rules to filter malicious parameter payloads.
Fix this in Identity Services Engine Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0339 — 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-2018-0339 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