Identity Services Engine SoftwareApplication · Cisco

CVE-2016-1402

HIGH · 7.5 CVSS v3.0 Published 2016-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Active Directory (AD) integration component in Cisco Identity Service Engine (ISE) before 1.2.0.899 patch 7, when AD group-membership authorization is enabled, allows remote attackers to cause a denial of service (authentication outage) via a crafted Password Authentication Protocol (PAP) authentication request, aka Bug ID CSCun25815.

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 versions before 1.2.0.899 patch 7 contain a denial of service vulnerability in the Active Directory integration component. When AD group-membership authorization is enabled, a remote attacker can send a specially crafted PAP (Password Authentication Protocol) authentication request that causes an authentication outage, preventing legitimate users from authenticating.

MitigationUpgrade Cisco ISE to version 1.2.0.899 patch 7 or later. As a temporary mitigation, consider disabling AD group-membership authorization if business requirements permit, though this may impact authorization policies.

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.2.0.899

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco ISE version
    Log into the ISE admin GUI and navigate to Administration > System > Logging > Debug Log Configuration, or use the CLI command 'show version' to determine the installed Cisco ISE software version.
    Affected if The installed version is 1.2.0.899 and does not have patch 7 applied.
  2. Confirm AD group-membership authorization is enabled
    In the ISE admin GUI, navigate to Policy > Policy Elements > Results > Authorization > Authorization Profiles, or check the relevant policy configuration to determine whether AD group-based authorization is active.
    Affected if AD group-membership authorization is enabled and the ISE version is 1.2.0.899 without patch 7.
  3. Verify PAP authentication protocol is in use
    Review the authentication settings in Policy > Authentication or check the active authentication protocols to see if PAP is permitted for external AD authentication.
    Affected if PAP authentication protocol is allowed for AD integrations on a vulnerable ISE version with AD group authorization enabled.

A Cisco ISE deployment is affected if it runs version 1.2.0.899 without patch 7 AND has AD group-membership authorization enabled with PAP authentication permitted.

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.2.0.899 patch 7 or later. As a temporary mitigation, consider disabling AD group-membership authorization if business requirements permit, though this may impact authorization policies.

Fix this in Identity Services Engine Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1402 — 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-2016-1402 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