dbcve.org
Prime Collaboration ProvisioningApplication · Cisco

CVE-2017-6792

MEDIUM · 6.5 CVSS v3.0 Published 2017-09-07
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 batch provisioning feature in Cisco Prime Collaboration Provisioning Tool could allow an authenticated, remote attacker to overwrite system files as root. The vulnerability is due to lack of input validation of the parameters in BatchFileName and Directory. An attacker could exploit this vulnerability by manipulating the parameters of the batch action file function. Cisco Bug IDs: CSCvd61766.

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

Path traversal vulnerability in Cisco Prime Collaboration Provisioning's batch provisioning feature allows authenticated remote attackers to overwrite system files as root due to missing input validation on BatchFileName and Directory parameters. An attacker can manipulate these parameters to write arbitrary files to the filesystem.

MitigationImplement strict input validation and path sanitization on BatchFileName and Directory parameters, using allowlist validation and rejecting any path containing traversal sequences (../). Apply least-privilege principles to limit the batch feature's file write capabilities. Apply Cisco's patch when available.

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:all versions

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

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

  1. Identify if Cisco Prime Collaboration Provisioning is installed
    Check for running processes named 'Cisco Prime Collaboration Provisioning' or look for the application in standard installation directories on the server
    Affected if The software is installed and running on the system
  2. Confirm the batch provisioning feature is enabled
    Access the application's web interface and navigate to the batch provisioning module, or check the application's configuration files for the batch provisioning feature status
    Affected if The batch provisioning feature is enabled and accessible via the web interface
  3. Verify authentication controls on the batch provisioning endpoint
    Review the application's access control configuration or test the batch provisioning URL without valid credentials to confirm authentication is enforced
    Affected if The batch provisioning feature can be accessed by authenticated users without additional restrictions
  4. Check for path traversal protection in batch request parameters
    Inspect the application's input validation logs or test submitting batch requests with Directory and BatchFileName parameters containing '../' sequences to observe if traversal is blocked
    Affected if The application accepts path traversal sequences in BatchFileName or Directory parameters without rejecting or sanitizing them
  5. Review web server logs for suspicious batch provisioning requests
    Examine access logs for the batch provisioning endpoint for unusual patterns such as '../' in parameter values or attempts to write to system directories
    Affected if Logs show path traversal attempts against the batch provisioning feature have occurred

A user is affected if Cisco Prime Collaboration Provisioning is installed with the batch provisioning feature enabled and accessible to authenticated users without proper input validation on BatchFileName and Directory parameters.

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

Implement strict input validation and path sanitization on BatchFileName and Directory parameters, using allowlist validation and rejecting any path containing traversal sequences (../). Apply least-privilege principles to limit the batch feature's file write capabilities. Apply Cisco's patch when available.

Fix this in Prime Collaboration Provisioning Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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