Prime CollaborationApplication · Cisco
CVE-2018-0322
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 management interface of Cisco Prime Collaboration Provisioning (PCP) could allow an authenticated, remote attacker to modify sensitive data that is associated with arbitrary accounts on an affected device. The vulnerability is due to a failure to enforce access restrictions on the Help Desk and User Provisioning roles that are assigned to authenticated users. This failure could allow an authenticated attacker to modify critical attributes of higher-privileged accounts on the device. A successful exploit could allow the attacker to gain elevated privileges on the device. This vulnerability affects Cisco Prime Collaboration Provisioning (PCP) Releases 12.1 and prior. Cisco Bug IDs: CSCvd61779.
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 · moderate confidenceBroken access control vulnerability in Cisco Prime Collaboration Provisioning web interface where Help Desk and User Provisioning role authentication fails to enforce proper authorization boundaries, allowing authenticated attackers to modify critical attributes of higher-privileged accounts and achieve privilege escalation.
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 CollaborationApplication
<= 12.1
Prime Collaboration ProvisioningApplication
<= 12.1CVSS 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.
-
Identify installed Cisco Prime Collaboration Provisioning versionAccess the web interface and navigate to Administration > Software Updates > Software Inventory, or check the version displayed on the login page or in the About section of the application.Affected if The displayed version is 12.1 or earlier.
-
Confirm the web interface is accessibleVerify that the Cisco Prime Collaboration Provisioning web interface (typically on port 443/8443) is reachable on the network.Affected if The web interface is exposed and reachable from network segments where lower-privileged users operate.
-
Review user role assignmentsLog in with administrative credentials and navigate to Users or Roles management. List all users assigned the Help Desk or User Provisioning roles.Affected if Users exist with Help Desk or User Provisioning roles in the system.
-
Check authorization controls on privileged account attributesAs a user with Help Desk or User Provisioning role, attempt to access or modify attributes of administrator-level accounts (such as changing email, phone, or other profile attributes).Affected if Lower-privileged roles can modify attributes of higher-privileged accounts without receiving authorization errors.
-
Audit role-based access control configurationNavigate to Administration > Users > Roles or similar RBAC configuration panel. Examine permission mappings for Help Desk and User Provisioning roles.Affected if These roles have permissions granted to modify or update attributes of accounts with higher privilege levels.
You are affected if the installed version is 12.1 or earlier AND lower-privileged roles (Help Desk or User Provisioning) can modify attributes of higher-privileged administrator accounts, indicating broken authorization boundaries.
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 dataUpgrade to a Cisco PCP version beyond 12.1 that addresses CSCvd61779, or apply available patches; verify role-based access controls properly restrict lower-privileged roles from modifying higher-privileged account attributes.
Fix this in Prime Collaboration
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0322 — 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-2018-0322 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