dbcve.org
Prime Collaboration ProvisioningApplication · Cisco

CVE-2017-6756

HIGH · 8.8 CVSS v3.0 Published 2017-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 UI Application of the Cisco Prime Collaboration Provisioning Tool through 12.2 could allow an unauthenticated, remote attacker to execute unwanted actions. The vulnerability is due to a lack of defense against cross-site request forgery (CSRF) attacks. An attacker could exploit this vulnerability by forcing the user's browser to perform any action authorized for that user. Cisco Bug IDs: CSCvc90280.

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

CSRF vulnerability in Cisco Prime Collaboration Provisioning Tool Web UI through version 12.2 allows unauthenticated remote attackers to force authenticated users' browsers to execute arbitrary actions the victim is authorized to perform, due to missing anti-CSRF tokens and protections.

MitigationApply Cisco patch for bug CSCvc90280; implement anti-CSRF tokens on all state-changing operations and configure SameSite cookie attributes.

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

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 the application process or service running on the server. Look for 'Cisco Prime Collaboration Provisioning' process, or check installed programs. The application typically runs on port 443 or 8443 for HTTPS web interface.
    Affected if The product is not installed on the system being assessed, so CSRF vulnerability does not apply.
  2. Verify the installed version is 12.2
    Access the Cisco Prime Collaboration Provisioning Web UI login page, then check the version information typically found in the About or Help section of the web interface, or check the application's version file if accessible via filesystem.
    Affected if The installed version is exactly 12.2, matching the affected version range.
  3. Confirm Web UI is accessible and authentication is enabled
    Attempt to access the web interface URL (typically https://server:443 or https://server:8443). Verify the login page loads and that authentication is required for access.
    Affected if The Web UI is accessible and requires authentication, meaning state-changing operations can potentially be forged via CSRF.
  4. Inspect HTTP responses for anti-CSRF token presence
    Log into the web interface and capture HTTP responses when performing state-changing actions (such as creating a user, modifying settings, or saving configurations). Examine the request headers and form parameters for anti-CSRF tokens or unique session tokens that would prevent CSRF attacks.
    Affected if State-changing requests do NOT include anti-CSRF tokens or unique per-request tokens in headers or form parameters, indicating vulnerability to CVE-2017-6756.

If Cisco Prime Collaboration Provisioning version 12.2 is running with its Web UI accessible, and HTTP requests for state-changing operations lack anti-CSRF tokens, the environment is vulnerable to CVE-2017-6756.

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 Cisco patch for bug CSCvc90280; implement anti-CSRF tokens on all state-changing operations and configure SameSite cookie attributes.

Fix this in Prime Collaboration Provisioning Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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