dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2018-0096

MEDIUM · 5.9 CVSS v3.0 Published 2018-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/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
A vulnerability in the role-based access control (RBAC) functionality of Cisco Prime Infrastructure could allow an authenticated, remote attacker to perform a privilege escalation in which one virtual domain user can view and modify another virtual domain configuration. The vulnerability is due to a failure to properly enforce RBAC for virtual domains. An attacker could exploit this vulnerability by sending an authenticated, crafted HTTP request to a targeted application. An exploit could allow the attacker to bypass RBAC policies on the targeted system to modify a virtual domain and access resources that are not normally accessible. Cisco Bug IDs: CSCvg36875.

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

This is an RBAC bypass vulnerability in Cisco Prime Infrastructure where virtual domain isolation is not properly enforced. An authenticated attacker with a crafted HTTP request can bypass RBAC policies to view and modify configurations in other virtual domains, achieving privilege escalation across domain boundaries.

MitigationApply the Cisco patch for CSCvg36875 to enforce proper RBAC isolation between virtual domains, and verify that cross-domain access is no longer possible after patching.

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
Prime InfrastructureApplication
Affected:= 3.2\(0.0\)= 3.3\(0.0\)

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

CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/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 Prime Infrastructure version
    Log into the Cisco Prime Infrastructure web interface and navigate to Administration > Settings > System Settings > Software Update, or run 'show version' via CLI to confirm the installed version is 3.2(0.0) or 3.3(0.0)
    Affected if The installed version matches 3.2(0.0) or 3.3(0.0)
  2. Verify virtual domains feature is configured
    In the Cisco Prime Infrastructure web interface, go to Administration > Users, Roles, and Virtual Domains > Virtual Domains to check if more than one virtual domain exists
    Affected if Multiple virtual domains are configured and active
  3. Review RBAC policy configuration
    Navigate to Administration > Users, Roles, and Virtual Domains > Role-Based Access Control (RBAC) and verify that domain-specific policies are defined to isolate configurations between virtual domains
    Affected if RBAC policies exist but may not be properly enforcing domain isolation boundaries
  4. Check authentication logs for cross-domain access attempts
    In Cisco Prime Infrastructure, go to Reports > Audit Logs or view system logs via CLI (show logs) for entries containing virtual domain ID changes or access to resources outside the assigned domain
    Affected if Audit logs show authenticated users accessing configurations or resources belonging to other virtual domains
  5. Test domain boundary enforcement
    As a user assigned to one virtual domain, attempt to access configuration data or device groups belonging to a different virtual domain using direct URL navigation or API requests
    Affected if A user can view or modify resources in another virtual domain despite being assigned to a different domain

You are affected if Cisco Prime Infrastructure version 3.2(0.0) or 3.3(0.0) is running with multiple virtual domains configured, and users can access resources outside their assigned domain boundaries.

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

Apply the Cisco patch for CSCvg36875 to enforce proper RBAC isolation between virtual domains, and verify that cross-domain access is no longer possible after patching.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2018-0096 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