Prime Collaboration ProvisioningApplication · Cisco

CVE-2017-6621

HIGH · 7.5 CVSS v3.0 Published 2017-05-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 interface of Cisco Prime Collaboration Provisioning could allow an unauthenticated, remote attacker to access sensitive data. The attacker could use this information to conduct additional reconnaissance attacks. The vulnerability is due to insufficient protection of sensitive data when responding to an HTTP request on the web interface. An attacker could exploit the vulnerability by sending a crafted HTTP request to the application to access specific system files. An exploit could allow the attacker to obtain sensitive information about the application which could include user credentials. This vulnerability affects Cisco Prime Collaboration Provisioning Software Releases 10.6 through 11.5. Cisco Bug IDs: CSCvc99626.

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

An information disclosure vulnerability in Cisco Prime Collaboration Provisioning web interface allows unauthenticated remote attackers to access sensitive system files via crafted HTTP requests. The vulnerability stems from insufficient protection of sensitive data in HTTP responses, potentially exposing user credentials.

MitigationApply the vendor patch for Cisco Bug ID CSCvc99626 to address this vulnerability. Until patched, restrict network access to the web interface and implement additional authentication layers.

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:= 9.0.0= 9.5.0= 10.0.0= 10.5.0= 10.5.1= 10.6.0= 10.6.2= 11.0.0= 11.1.0= 11.5.0

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

CVSS:3.0/AV:N/AC:L/PR:N/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. Identify Cisco Prime Collaboration Provisioning installation
    Locate the Cisco Prime Collaboration Provisioning installation directory or check system services for the application
    Affected if The application is installed on the system
  2. Determine installed version
    Check the version of Cisco Prime Collaboration Provisioning using the application's built-in version command, help interface, or administrative console
    Affected if The installed 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, 11.0.0, 11.1.0, or 11.5.0
  3. Verify web interface accessibility
    Confirm the Cisco Prime Collaboration Provisioning web interface is accessible from the network by testing HTTP/HTTPS access to the application URL
    Affected if The web interface is exposed and reachable over the network

A user is affected if Cisco Prime Collaboration Provisioning is installed with a version matching 9.0.0, 9.5.0, 10.0.0, 10.5.0, 10.5.1, 10.6.0, 10.6.2, 11.0.0, 11.1.0, or 11.5.0 and the web interface is accessible.

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 Cisco Bug ID CSCvc99626 to address this vulnerability. Until patched, restrict network access to the web interface and implement additional authentication layers.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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