CVE intelligence and bounded remediation

CVE-2017-6621 — Cisco Prime Collaboration Provisioning security vulnerability

High CVSS 7.5

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.

Severity
High
CVSS
7.5 (3.0)
Published
2017-05-18
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-200

Affected products

  • cisco / prime_collaboration_provisioning / 9.0.0
  • cisco / prime_collaboration_provisioning / 9.5.0
  • cisco / prime_collaboration_provisioning / 10.0.0
  • cisco / prime_collaboration_provisioning / 10.5.0
  • cisco / prime_collaboration_provisioning / 10.5.1
  • cisco / prime_collaboration_provisioning / 10.6.0

Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Information disclosure and sensitive data exposure

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
  • Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
  • Review metadata, timing, status, length, and existence signals as well as direct content disclosure.

Remediate safely

  • Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
  • Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
  • Update the affected component and add synthetic-data tests for response, error, observability, and export paths.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.