Prime CollaborationApplication · Cisco
CVE-2018-0336
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 batch provisioning feature of Cisco Prime Collaboration Provisioning could allow an authenticated, remote attacker to escalate privileges to the Administrator level. The vulnerability is due to insufficient authorization enforcement on batch processing. An attacker could exploit this vulnerability by uploading a batch file and having the batch file processed by the system. A successful exploit could allow the attacker to escalate privileges to the Administrator level. Cisco Bug IDs: CSCvd86578.
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 privilege escalation vulnerability exists in the batch provisioning feature of Cisco Prime Collaboration Provisioning. An authenticated remote attacker can upload a specially crafted batch file that, when processed by the system, grants them Administrator-level privileges. The vulnerability stems from insufficient authorization enforcement during batch file processing, allowing standard users to escalate beyond their assigned privileges.
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.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 Cisco Prime Collaboration installation and versionCheck for Cisco Prime Collaboration software on the system. Look for installation directories, service processes, or use system inventory tools to determine if the product is present and retrieve its version number.Affected if The installed version is Cisco Prime Collaboration version 12.1 exactly.
-
Verify batch provisioning feature is accessibleLog into the Cisco Prime Collaboration web interface or check system configuration to determine whether the batch provisioning feature is enabled and accessible to authenticated users.Affected if The batch provisioning feature is enabled and available to non-administrator user accounts.
-
Check for standard user access to batch provisioningReview user accounts and their assigned roles within Cisco Prime Collaboration. Identify whether standard or non-administrator users have permissions to access or use the batch provisioning functionality.Affected if Standard (non-Administrator) user accounts have been granted access to the batch provisioning feature.
-
Inspect for unexpected administrator-level privilegesReview user privilege assignments in the system. Compare current user privilege levels against expected baseline permissions. Look for standard users who unexpectedly possess Administrator-level roles or permissions.Affected if Standard user accounts have been granted Administrator-level privileges that were not explicitly assigned through normal administration.
A user is affected if Cisco Prime Collaboration version 12.1 is running with the batch provisioning feature accessible to non-administrator accounts, and standard users have acquired Administrator-level privileges they were not assigned.
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 the vendor patch from Cisco (CSCvd86578) when available. Until patched, consider restricting access to the batch provisioning feature to only trusted Administrator accounts and monitoring for unauthorized privilege escalation.
Fix this in Prime Collaboration
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0336 — 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-0336 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