Identity Services Engine SoftwareApplication · Cisco
CVE-2015-4267
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 · uneditedCross-site request forgery (CSRF) vulnerability in the web framework in Cisco Identity Services Engine (ISE) 1.2(0.793), 1.3(0.876), 1.4(0.109), 2.0(0.147), and 2.0(0.169) allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCus09940.
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 confidenceCross-site request forgery (CSRF) vulnerability in Cisco ISE's web framework allows remote attackers to hijack authentication of arbitrary users by tricking authenticated users into submitting malicious 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 Engine SoftwareApplication
= 1.2\(0.793\)= 1.3\(0.876\)= 1.4\(0.181\)= 1.4\(0.876\)= 2.0\(0.147\)= 2.0\(0.169\)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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 Cisco ISE by checking running services, installed applications, or by accessing the web interface on typical ports (443, 8443). Confirm the product is Cisco Identity Services Engine.Affected if Cisco ISE web interface is accessible and the product is running
-
Determine installed Cisco ISE versionAccess the ISE admin web interface and navigate to Administration > System > Server > Server Settings, or use the CLI command 'show version' to retrieve the software version.Affected if Version matches any of: 1.2(0.793), 1.3(0.876), 1.4(0.181), 1.4(0.876), 2.0(0.147), 2.0(0.169)
-
Verify web framework is enabledConfirm the ISE web admin interface is active and users can authenticate. CSRF attacks require an authenticated session to exploit.Affected if Web interface is enabled and users are authenticated
User is affected if Cisco ISE is running with version 1.2(0.793), 1.3(0.876), 1.4(0.181), 1.4(0.876), 2.0(0.147), or 2.0(0.169) and the web interface is accessible.
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 Cisco-provided patches or upgrades to a fixed version of Cisco ISE. Implement anti-CSRF tokens and validate Origin/Referer headers as compensating controls until the patch is applied.
Fix this in Identity Services Engine Software
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4267 — 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-4267 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