Prime Collaboration ProvisioningApplication · Cisco

CVE-2017-6704

MEDIUM · 6.5 CVSS v3.0 Published 2017-07-04
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 application in the Cisco Prime Collaboration Provisioning tool could allow an authenticated, remote attacker to perform arbitrary file downloads that could allow the attacker to read files from the underlying filesystem. More Information: CSCvc90335. Known Affected Releases: 12.1.

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 confidence

A path traversal vulnerability in the web interface of Cisco Prime Collaboration Provisioning version 12.1 allows an authenticated remote attacker to download arbitrary files from the server's filesystem by manipulating file path parameters in HTTP requests.

MitigationApply the vendor patch for CSCvc90335 from Cisco. If no patch is available, restrict web application access to only trusted authenticated users and implement input validation/path traversal protection at the application or WAF layer to prevent directory traversal sequences in file request parameters.

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
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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cisco Prime Collaboration Provisioning is installed
    Check for the presence of Cisco Prime Collaboration Provisioning on the system by looking for its installation directory, service, or by querying installed software packages if available
    Affected if The product is not installed on the system
  2. Confirm the installed version is 12.1
    Locate the version information for Cisco Prime Collaboration Provisioning, typically found in the software itself, installation logs, or system inventory, and verify it equals 12.1
    Affected if The installed version is exactly 12.1 (any other version is not affected by this specific CVE)
  3. Determine if the web interface is accessible
    Check if the Cisco Prime Collaboration Provisioning web interface port (default HTTPS ports 443 or 8443) is listening and reachable on the server
    Affected if The web interface is exposed and accessible (even internally)
  4. Check if authentication is enabled on the web interface
    Verify that authentication is required to access the web interface by attempting to reach the login page or checking the web server configuration
    Affected if The web interface permits unauthenticated access to login or certain endpoints (authenticated access is required for this exploit but weak auth increases risk)

A system is affected if Cisco Prime Collaboration Provisioning version 12.1 is installed and its web interface is accessible, allowing an authenticated user to potentially exploit the path traversal vulnerability to read arbitrary files.

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 for CSCvc90335 from Cisco. If no patch is available, restrict web application access to only trusted authenticated users and implement input validation/path traversal protection at the application or WAF layer to prevent directory traversal sequences in file request parameters.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6704 — 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-2017-6704 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