Prime Collaboration ProvisioningApplication · Cisco
CVE-2017-6759
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 UpgradeManager of the Cisco Prime Collaboration Provisioning Tool 12.1 could allow an authenticated, remote attacker to write arbitrary files as root on the system. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by triggering the upgrade package installation functionality. Cisco Bug IDs: CSCvc90304.
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 path traversal/file write vulnerability in Cisco Prime Collaboration Provisioning Tool 12.1's UpgradeManager allows authenticated remote attackers to write arbitrary files as root due to insufficient input validation during the upgrade package installation process.
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 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Prime Collaboration Provisioning installationLocate the Cisco Prime Collaboration Provisioning installation directory and confirm the product is present. Check common installation paths or use system inventory tools to identify if this application is running on the system.Affected if The product is installed and running on the system
-
Verify exact version is 12.1Check the installed version of Cisco Prime Collaboration Provisioning. Look for version information in the application GUI, about page, or check installation logs and version files in the application directory.Affected if The installed version is exactly 12.1 (the only affected version)
-
Confirm UpgradeManager component is accessibleCheck if the UpgradeManager web interface is accessible. This is typically accessed via the application's web portal. Verify whether the UpgradeManager functionality is enabled and reachable.Affected if UpgradeManager is accessible without additional restrictions
-
Review UpgradeManager authentication configurationExamine the authentication and access control settings for the UpgradeManager functionality. Check if administrative access is properly restricted or if anonymous/unauthenticated access is possible.Affected if UpgradeManager allows access without proper authentication controls or is accessible to untrusted users
The system is affected if Cisco Prime Collaboration Provisioning version 12.1 is installed and the UpgradeManager component is accessible, allowing authenticated attackers to perform arbitrary file writes.
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 (CSCvc90304) and restrict administrative access to the UpgradeManager functionality to trusted, authenticated users only.
Fix this in Prime Collaboration Provisioning
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6759 — 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-2017-6759 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