Identity Services EngineApplication · Cisco
CVE-2020-3467
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 web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to modify parts of the configuration on an affected device. The vulnerability is due to improper enforcement of role-based access control (RBAC) within the web-based management interface. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to modify parts of the configuration. The modified configuration could either allow unauthorized devices onto the network or prevent authorized devices from accessing the network. To exploit this vulnerability, an attacker would need valid Read-Only Administrator credentials.
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 confidenceA vulnerability in Cisco ISE's web-based management interface allows authenticated Read-Only Administrators to modify configuration via crafted HTTP requests due to improper RBAC enforcement. This authorization bypass enables privilege escalation within the application, potentially allowing unauthorized network access or blocking legitimate devices.
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 EngineApplication
<= 2.4= 2.4\(0.357\)= 2.4.0.357= 2.5= 2.6\(0.156\)= 2.6.0= 2.6.0.156= 2.7= 2.7\(0.356\)= 2.7.0.356CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco ISE installation and versionLog into the Cisco ISE admin web interface and navigate to Administration > System > Licensing, or run 'show version' via CLI to retrieve the installed Cisco ISE version number.Affected if The installed version matches one of the affected versions: <=2.4, 2.4.0.357, 2.5, 2.6, 2.6.0.156, 2.7, or 2.7.0.356.
-
Verify presence of Read-Only Administrator accountsIn the Cisco ISE admin interface, navigate to Administration > Identity Management > Identities > Users and look for accounts assigned the 'Read-Only Admin' role, or query via CLI with 'show running-config | include user' to list admin accounts and their privilege levels.Affected if Any Read-Only Administrator accounts exist in the system.
-
Review RBAC policy configurationIn the Cisco ISE admin interface, go to Administration > System > Admin Access > Authorization > RBAC Policy to examine role-based access control rules and verify which privileges are assigned to Read-Only Administrators.Affected if The RBAC policy permits Read-Only Administrators to perform configuration modifications or if custom rules grant elevated privileges.
-
Examine admin activity logs for unauthorized changesIn the Cisco ISE admin interface, go to Operations > RADIUS > Live Logs or use the Audit Logs feature to search for configuration changes performed by Read-Only Administrator accounts.Affected if Audit logs show configuration modifications made by accounts with Read-Only Administrator role.
-
Check for unauthorized network device or endpoint entriesNavigate to Work Centers > Network Access > Network Devices or posture and endpoint dashboards to identify any newly added network devices, IP ranges, or endpoint entries that were not created by full administrators.Affected if New network devices, access policy changes, or endpoint entries exist that were not authorized by Full Administrator accounts.
You are affected if Cisco ISE is running an affected version (2.4 through 2.7.0.356) and any Read-Only Administrator accounts exist or have made configuration changes.
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's official patch for CVE-2020-3467 when available. Until then, restrict Read-Only Administrator access to only trusted personnel and monitor for unauthorized configuration changes.
Fix this in Identity Services Engine
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-2020-3467 — 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-2020-3467 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