Identity Services Engine SoftwareApplication · Cisco
CVE-2017-3835
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 sponsor portal of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to access notices owned by other users, because of SQL Injection. More Information: CSCvb15627. Known Affected Releases: 1.4(0.908).
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 confidenceSQL injection vulnerability in the Cisco ISE sponsor portal allows authenticated remote attackers to access notices belonging to other users by manipulating SQL queries. The vulnerability stems from improper input validation in the portal's database queries.
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.4\(0.908\)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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check Cisco ISE versionLog into the Cisco ISE admin GUI, navigate to Administration > System > Licensing, or use the CLI command 'show version' to determine the installed software versionAffected if The installed version is exactly 1.4(0.908)
-
Verify sponsor portal is enabledIn Cisco ISE admin GUI, navigate to Administration > Portal Settings > Sponsor Portals, or check via CLI: 'show running-config | include sponsor'Affected if The sponsor portal is enabled and the version is 1.4(0.908)
-
Review sponsor portal access logs for anomalous notice queriesIn Cisco ISE, go to Operations > RADIUS > Live Logs, or check sponsor portal audit logs for SQL query patterns and access to notices belonging to other user IDsAffected if Logs show SQL query anomalies or unauthorized access to other users' notice records
-
Check for unauthorized notice access via sponsor portalReview sponsor portal session logs and look for instances where a sponsor user accessed notices with ID values outside their expected range, or accessed notices belonging to other sponsor accountsAffected if Evidence exists of cross-user notice access through the sponsor portal interface
A user is affected if running Cisco ISE version 1.4(0.908) with the sponsor portal feature enabled, as this specific version contains the SQL injection flaw in the sponsor portal component.
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 ISE patch for this vulnerability; if no patch is available, implement web application firewall (WAF) rules to detect and block SQL injection attempts as a temporary mitigation.
Fix this in Identity Services Engine Software
Scoped from the published advisory
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3835 — 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-2017-3835 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