Prime CollaborationApplication · Cisco
CVE-2018-0391
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 password change function of Cisco Prime Collaboration Provisioning could allow an authenticated, remote attacker to cause the system to become inoperable. The vulnerability is due to insufficient validation of a password change request. An attacker could exploit this vulnerability by changing a specific administrator account password. A successful exploit could allow the attacker to cause the affected device to become inoperable, resulting in a denial of service (DoS) condition. This vulnerability affects Cisco Prime Collaboration Provisioning (PCP) Releases 12.2 and prior. Cisco Bug IDs: CSCvd86586.
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 confidenceA denial of service vulnerability in Cisco Prime Collaboration Provisioning's password change function allows an authenticated attacker to make the system inoperable by changing a specific administrator account password. The vulnerability stems from insufficient validation of password change requests, which can be exploited to cause the affected device to fail.
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.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed versionAccess the Cisco Prime Collaboration Provisioning admin console or use CLI to retrieve the software version. Typically found in the About or System Information section of the web interface, or via 'show version' command in CLI.Affected if Version equals 12.1 or is 12.2 or lower (12.2, 12.1, 12.0, etc.)
-
Verify administrative accounts existLog into the administration interface and navigate to User Management or Administrators section to confirm at least one administrator-level account is configured.Affected if Administrative accounts are present in the system - the vulnerability is triggered when a password change is attempted on the specific affected administrator account.
-
Confirm password change interface accessibilityCheck if the password change or user management interface is accessible to authenticated users. Navigate to the account settings or admin password management area.Affected if The password change function is enabled and accessible to authenticated users - this is the feature that contains the vulnerability.
-
Review system availabilityCheck if the Cisco Prime Collaboration Provisioning system is operational and responsive. Attempt to access the main admin dashboard and core services.Affected if The system is unresponsive, crashing, or inoperable after a password change operation - this indicates successful exploitation causing the DoS condition.
You are affected if your installed version is Cisco Prime Collaboration 12.1 or Cisco Prime Collaboration Provisioning 12.2 or lower, and the password change function is accessible to authenticated users.
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 for Cisco Bug ID CSCvd86586 when available. Until then, restrict access to administrator-level accounts and monitor for unauthorized password modification attempts on the specific affected administrator account.
Fix this in Prime Collaboration
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0391 — 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-0391 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