Identity Services Engine SoftwareApplication · Cisco

CVE-2015-4182

MEDIUM · 5.5 CVSS v2.0 Published 2015-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The administrative web interface in Cisco Identity Services Engine (ISE) before 1.3 allows remote authenticated users to bypass intended access restrictions, and obtain sensitive information or change settings, via unspecified vectors, aka Bug ID CSCui72087.

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

Cisco ISE before version 1.3 contains an access control bypass vulnerability in its administrative web interface. Authenticated users can circumvent intended privilege restrictions to access sensitive information or modify system settings they should not have permission to view or change.

MitigationUpgrade Cisco ISE to version 1.3 or later to remediate this access control bypass vulnerability. Additionally, review administrative user accounts and privileges to ensure least-privilege principles are enforced.

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
Affected:= 1.0.4.573= 1.0_base= 1.1= 1.2= 1.2\(0.747\)= 1.2\(0.899\)= 1.2\(1.901\)= 1.3= 1.4

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:S/C:P/I:P/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 installation
    Check if Cisco Identity Services Engine is installed on the system by looking for the ISE service or process, or by accessing the admin web interface URL (typically https://<ise-hostname>/admin/)
    Affected if The product is not Cisco ISE, this check does not apply. If Cisco ISE is present, proceed to version check.
  2. Determine installed Cisco ISE version
    Log into the Cisco ISE admin web interface and navigate to Administration > System > Licensing, or use the CLI command 'show version' to display the running software version
    Affected if The installed version matches one of the following: 1.0.4.573, 1.0_base, 1.1, 1.2, 1.2(0.747), 1.2(0.899), 1.2(1.901), 1.3, or 1.4. Compare your version against this list to determine if you are within the affected range.
  3. Verify admin web interface is accessible
    Confirm the Cisco ISE administrative web interface (typically on port 443 or 8443) is reachable from network locations where untrusted users could authenticate
    Affected if The admin web interface is exposed to users who have valid but limited-privilege Cisco ISE accounts, allowing them to attempt privilege escalation.
  4. Review administrative user accounts
    Check the Cisco ISE admin panel for user accounts with elevated privileges under Administration > Identity Management > Identities > Users
    Affected if There exist authenticated users with limited privileges who could potentially exploit this access control bypass to gain unauthorized access to sensitive information or modify system settings.

A user is affected if Cisco ISE version 1.0.4.573, 1.0_base, 1.1, 1.2, 1.2(0.747), 1.2(0.899), 1.2(1.901), 1.3, or 1.4 is running and the admin web interface is accessible to authenticated users with restricted privileges.

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

Upgrade Cisco ISE to version 1.3 or later to remediate this access control bypass vulnerability. Additionally, review administrative user accounts and privileges to ensure least-privilege principles are enforced.

Fix this in Identity Services Engine Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4182 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4182 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