Prime CollaborationApplication · Cisco

CVE-2018-15450

MEDIUM · 6.5 CVSS v3.1 Published 2018-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 web-based UI of Cisco Prime Collaboration Assurance could allow an authenticated, remote attacker to overwrite files on the file system. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by using a specific UI input field to provide a custom path location. A successful exploit could allow the attacker to overwrite files on the file system.

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 confidence

This is a path traversal vulnerability in Cisco Prime Collaboration Assurance's web UI that allows authenticated attackers to overwrite arbitrary files on the filesystem by providing custom path locations through insufficiently validated input fields. The attacker needs valid authentication credentials to exploit this flaw.

MitigationApply the vendor patch from Cisco, implement strict input validation and path sanitization on all file-related UI fields, and enforce least-privilege access controls to limit which authenticated users can access file operations.

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
Affected:= 12.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm Cisco Prime Collaboration installation
    Locate the installation directory (typically under /opt/cisco/prime or C:\Program Files\Cisco\Prime on Windows) or check running processes for 'prime' or 'collaboration' services
    Affected if Cisco Prime Collaboration software is installed on the system
  2. Verify the installed version
    Check the version by reviewing installation logs, the about page in the web UI, or running 'show version' command if CLI access is available
    Affected if The installed version is exactly 12.1
  3. Determine if the web UI is exposed
    Check if ports 443, 8443, or 8080 are listening and accessible (for example, using netstat or nmap to scan local ports or remote endpoints)
    Affected if The web interface is accessible over the network
  4. Confirm authentication is enabled
    Verify that user accounts exist for the web UI by checking the local user database or authentication configuration files in the installation directory
    Affected if Valid user credentials can be obtained or created for the web interface
  5. Identify file operation access
    Log into the web UI and navigate to any features that involve file upload, export, or write operations (such as backup/restore, report generation, or configuration import)
    Affected if Authenticated users have access to file-related operations in the web UI

User is affected if Cisco Prime Collaboration version 12.1 is running with its web UI accessible and authenticated users can access file operation features.

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 vendor patch from Cisco, implement strict input validation and path sanitization on all file-related UI fields, and enforce least-privilege access controls to limit which authenticated users can access file operations.

Fix this in Prime Collaboration Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-15450 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15450 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