Identity Services Engine SoftwareApplication · Cisco
CVE-2015-6317
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 · uneditedCisco Identity Services Engine (ISE) before 2.0 allows remote authenticated users to bypass intended web-resource access restrictions via a direct request, aka Bug ID CSCuu45926.
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 confidenceCisco Identity Services Engine (ISE) versions before 2.0 contain an authorization bypass vulnerability where remote authenticated users can bypass intended web-resource access restrictions by submitting direct requests to privileged endpoints. This allows lower-privileged users to access resources outside their authorized scope.
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
= 1.0.4.573= 1.0_base= 1.0_mr_base= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1_base= 1.2\(0.747\)= 1.2\(0.793\)= 1.2\(1.198\)= 1.2\(1.901\)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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify Cisco ISE is installedCheck for Cisco ISE processes or service on the system. On the ISE CLI, run 'show version' or check the application directory at /opt/CSCOISE (if local).Affected if Cisco ISE software is present on the system
-
Determine installed ISE versionRun 'show version' on the ISE CLI or access the web interface and check the Dashboard for the software version displayed.Affected if Version displayed is 1.0.x, 1.1.x, or 1.2.x (any build listed in the affected versions)
-
Confirm version is before 2.0Compare the installed version number against the affected versions list. Any version = 1.0.4.573, 1.0_base, 1.0_mr_base, 1.1.x, 1.1_base, or 1.2.x is vulnerable.Affected if Installed version matches any of the listed affected versions (1.0.4.573 through 1.2(1.901))
-
Check if web interface is accessibleAttempt to access the ISE web interface (https://<ise-host>/admin) or check if the Cisco ISE Web Engine service is running.Affected if Web interface is exposed and the ISE version is before 2.0
A system is affected if Cisco ISE is installed with any version from 1.0.4.573 through 1.2(1.901) and the web interface is accessible to authenticated users.
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 dataUpgrade Cisco ISE to version 2.0 or later to obtain the fix for this authorization bypass vulnerability.
Fix this in Identity Services Engine Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6317 — 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-2015-6317 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