Prime Collaboration AssuranceApplication · Cisco
CVE-2015-6330
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 · uneditedCross-site request forgery (CSRF) vulnerability in Cisco Prime Collaboration Assurance 10.5(1) and 10.6 allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCus62712.
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 confidenceCross-site request forgery (CSRF) vulnerability in Cisco Prime Collaboration Assurance versions 10.5(1) and 10.6 allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into submitting malicious requests.
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 AssuranceApplication
= 10.5.1= 10.6.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 version of Cisco Prime Collaboration AssuranceAccess the application admin interface and navigate to Help > About, or check the software release notes included with the installation. Compare the version number against the affected versions: 10.5(1) and 10.6.0.Affected if The installed version is exactly 10.5.1 or 10.6.0
-
Inspect state-changing forms for anti-CSRF token presenceLog into Cisco Prime Collaboration Assurance as an authenticated user. Capture HTTP requests when performing state-changing actions such as creating, modifying, or deleting objects. Examine the POST requests for the presence of a unique, unpredictable token parameter (such as 'csrfToken', 'token', or similar) in the request body.Affected if State-changing operations do not include anti-CSRF tokens in the request parameters
-
Verify Referer or Origin header validationUsing a web proxy, capture HTTP requests to the application. Observe whether the server validates the Referer or Origin header by issuing a request with a missing or mismatched Referer/Origin header and checking if the request is rejected.Affected if The server accepts requests without validating the Referer or Origin header, allowing requests from arbitrary origins
-
Check for SameSite cookie attributesCapture authenticated session cookies from the application using browser developer tools or a proxy. Examine the Set-Cookie headers to determine if the 'SameSite' attribute is set to 'Strict' or 'Lax' on session cookies.Affected if Session cookies do not have the SameSite attribute set, or it is set to 'None' without Secure flags
A user is affected if they are running Cisco Prime Collaboration Assurance version 10.5.1 or 10.6.0 AND the application lacks anti-CSRF tokens on state-changing operations, does not validate Referer/Origin headers, and does not use SameSite cookie attributes.
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 anti-CSRF tokens (synchronizer token pattern) on all state-changing operations, validate the Referer/Origin header on requests, and consider implementing SameSite cookie attributes to mitigate CSRF attacks.
Fix this in Prime Collaboration Assurance
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6330 — 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-2015-6330 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