dbcve.org
Prime Collaboration ProvisioningApplication · Cisco

CVE-2017-6705

MEDIUM · 5.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 →
57/100
Remediation priority · Elevated
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 filesystem of the Cisco Prime Collaboration Provisioning tool could allow an authenticated, local attacker to acquire sensitive information. More Information: CSCvc82973. 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 · moderate confidence

A filesystem vulnerability in Cisco Prime Collaboration Provisioning tool allows an authenticated local attacker to read sensitive information from the filesystem. The issue stems from improper access controls on certain filesystem resources.

MitigationApply the vendor patch for CVE-2017-6705 (reference CSCvc82973) or upgrade to a Cisco Prime Collaboration Provisioning release beyond the affected 12.1 version.

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

CVSS:3.0/AV:L/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. Locate Cisco Prime Collaboration Provisioning installation
    Search for the installation directory - typical paths include /opt/cisco/pcp or C:\Program Files\Cisco\Prime Collaboration Provisioning. Check for the 'pcp' or 'provisioning' directory and verify the product name.
    Affected if The product is installed in the system
  2. Identify installed version
    Check version files in the installation directory, typically found in version.txt, about.properties, or the WEB-INF/web.xml descriptor. The version may also be displayed on the web interface login page.
    Affected if The installed version is exactly 12.1 (matches the affected range)
  3. Verify web service is running
    Check if the Cisco Prime Collaboration Provisioning web interface is accessible. Use command 'netstat -an | grep 8080' or 'netstat -an | grep 8443' to verify HTTP/HTTPS listeners are active, or attempt to access the login page.
    Affected if The web service is running and reachable
  4. Check for authenticated access to filesystem resources
    Log into the web interface with valid credentials. Navigate to file download or export features that may allow access to filesystem paths. Look for directory traversal or improper path access patterns.
    Affected if An authenticated user can access files outside their intended directory scope
  5. Verify access control configuration
    Examine the application's access control logs or configuration files for filesystem resource permissions. Look for any misconfigured file access permissions in the application's data directories.
    Affected if Access controls on filesystem resources are improperly configured

The environment is affected if Cisco Prime Collaboration Provisioning version 12.1 is installed and the web service is accessible, allowing an authenticated user to read sensitive filesystem information due to improper access controls.

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 CVE-2017-6705 (reference CSCvc82973) or upgrade to a Cisco Prime Collaboration Provisioning release beyond the affected 12.1 version.

Fix this in Prime Collaboration Provisioning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6705 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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