Prime Collaboration ProvisioningApplication · Cisco
CVE-2017-6636
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 interface of Cisco Prime Collaboration Provisioning Software (prior to Release 11.1) could allow an authenticated, remote attacker to view any file on an affected system. The vulnerability exists because the affected software does not perform proper input validation of HTTP requests and fails to apply role-based access controls (RBACs) to requested HTTP URLs. An attacker could exploit this vulnerability by sending a crafted HTTP request that uses directory traversal techniques to submit a path to a desired file location on an affected system. A successful exploit could allow the attacker to view any file on the system. Cisco Bug IDs: CSCvc99604.
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 confidenceThis is a path traversal vulnerability combined with an authorization bypass in Cisco Prime Collaboration Provisioning's web interface. An authenticated, remote attacker can send crafted HTTP requests using directory traversal sequences (e.g., ../../) to bypass role-based access controls and read arbitrary files on the affected system. The vulnerability stems from missing input validation and RBAC enforcement on HTTP URL requests.
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
= 9.0.0= 9.5.0= 10.0.0= 10.5.0= 10.5.1= 10.6.0= 10.6.2= 11.0.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Confirm Cisco Prime Collaboration Provisioning is installedCheck for the presence of the Cisco Prime Collaboration Provisioning application on the system by looking for the service process or consulting the application's built-in version information page typically accessible via the web interface at /pcp/Affected if The application is found and running on the system
-
Identify the installed versionAccess the application's web interface and navigate to the About or Version page, typically found under the Help or Administration section, to retrieve the exact version numberAffected if The version matches any of the following: 9.0.0, 9.5.0, 10.0.0, 10.5.0, 10.5.1, 10.6.0, 10.6.2, or 11.0.0
-
Verify the web interface is accessibleAttempt to reach the application's login page over HTTP/HTTPS to confirm the web interface is exposedAffected if The web interface is reachable from a network location
-
Review HTTP access logs for traversal patternsExamine web server logs for requests containing directory traversal sequences such as ../ or ..%2F in the URL parameters, especially targeting sensitive system pathsAffected if Suspicious traversal sequences are found in the HTTP logs, particularly from authenticated sessions accessing unexpected file locations
You are affected if Cisco Prime Collaboration Provisioning is installed and the version matches any of the affected releases (9.0.0 through 11.0.0) with the web interface accessible to network 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 dataUpgrade Cisco Prime Collaboration Provisioning to Release 11.1 or later where the patch has been applied. Limit web interface exposure to trusted networks and monitor for anomalous HTTP requests containing traversal sequences.
Fix this in Prime Collaboration Provisioning
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-2017-6636 — 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-6636 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