Prime Collaboration ProvisioningApplication · Cisco
CVE-2017-6793
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 · uneditedA vulnerability in the Inventory Management feature of Cisco Prime Collaboration Provisioning Tool could allow an authenticated, remote attacker to view sensitive information on the system. The vulnerability is due to insufficient protection of restricted information. An attacker could exploit this vulnerability by accessing unauthorized information via the user interface. Cisco Bug IDs: CSCvd61932.
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 confidenceAn information disclosure vulnerability in Cisco Prime Collaboration Provisioning Tool's Inventory Management feature allows authenticated remote attackers to view sensitive system information they are not authorized to access, due to insufficient protection of restricted data in the web interface.
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
all versionsCVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco Prime Collaboration Provisioning is installedCheck for the application by reviewing installed software on the system, or by accessing the web management interface on the default ports (typically 443 or 8443). Look for the Cisco Prime Collaboration Provisioning login page.Affected if The product is installed and running
-
Verify the Inventory Management feature is accessibleLog into the web interface and navigate to the Inventory Management section. This feature is typically found under the 'Inventory' or 'Resource' management sections of the web UI.Affected if The Inventory Management feature is present and accessible to the user account
-
Check web interface network exposureReview firewall rules and network configuration to determine if the Cisco Prime Collaboration Provisioning web interface is exposed to network segments outside the trusted management network.Affected if The web management interface is reachable from untrusted network segments or the internet
-
Audit user access logs for the Inventory Management featureReview access logs for the web interface, specifically looking for the Inventory Management feature endpoints. Check for access patterns by users who should not have authorization to view sensitive system inventory data.Affected if There are log entries showing access to inventory data by users lacking proper authorization
-
Review user account privilegesExamine the user role assignments in Cisco Prime Collaboration Provisioning to identify accounts that have access to Inventory Management but should not have visibility into restricted system information.Affected if Non-administrator or less-privileged accounts have access to the Inventory Management feature
You are affected if Cisco Prime Collaboration Provisioning is installed and the Inventory Management web interface is accessible to authenticated users who should not have authorization to view restricted system information.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Cisco software update for CSCvd61932 when available. Restrict network access to the management interface to authorized personnel only and audit user access patterns.
Fix this in Prime Collaboration Provisioning
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6793 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6793 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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