Prime Collaboration ProvisioningApplication · Cisco
CVE-2017-6703
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 web application in the Cisco Prime Collaboration Provisioning tool could allow an unauthenticated, remote attacker to hijack another user's session. More Information: CSCvc90346. Known Affected Releases: 12.1.
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 confidenceA session hijacking vulnerability in Cisco Prime Collaboration Provisioning's web application allows an unauthenticated, remote attacker to capture and reuse another user's session token, gaining unauthorized access to that user's session without credentials.
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
= 11.2_base= 11.5.0= 11.6_base= 12.1_baseCVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/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.
-
Identify the installed Cisco Prime Collaboration Provisioning versionAccess the application's about page or use the CLI command 'show version' on the appliance, or check the software installed packagesAffected if The version displayed matches 11.2_base, 11.5.0, 11.6_base, or 12.1_base
-
Confirm the web application interface is accessibleAttempt to reach the Cisco Prime Collaboration Provisioning web portal via HTTPS or HTTP from a client systemAffected if The web interface responds and accepts authentication requests, making it reachable for session hijacking attacks
-
Check if session tokens are exposed in URLs or logsReview browser developer tools or application logs for session identifiers being transmitted in URLs,Referer headers, or written to accessible log filesAffected if Session tokens appear in URLs, are logged without masking, or are visible in client-side scripts
You are affected if the installed Cisco Prime Collaboration Provisioning version matches 11.2_base, 11.5.0, 11.6_base, or 12.1_base AND the web application is accessible over the network.
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 dataImplement secure session token generation with high-entropy random values, enforce secure cookie attributes (HttpOnly, Secure, SameSite), add session binding to client attributes, and configure appropriate session timeouts.
Fix this in Prime Collaboration Provisioning
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6703 — 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-6703 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