dbcve.org
Prime Collaboration AssuranceApplication · Cisco

CVE-2015-4304

HIGH · 9.0 CVSS v2.0 Published 2015-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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
The web framework in Cisco Prime Collaboration Assurance before 10.5.1.53684-1 allows remote authenticated users to bypass intended access restrictions, and create administrative accounts or read data from arbitrary tenant domains, via a crafted URL, aka Bug IDs CSCus62671 and CSCus62652.

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

The web framework in Cisco Prime Collaboration Assurance before version 10.5.1.53684-1 contains an access control bypass vulnerability. Authenticated users can exploit this through crafted URLs to create administrative accounts or read data from arbitrary tenant domains, indicating a broken authorization mechanism in multi-tenant isolation.

MitigationUpgrade to Cisco Prime Collaboration Assurance version 10.5.1.53684-1 or later to obtain the vendor patch. Until patched, monitor for unauthorized administrative account creation and restrict user access to only necessary tenant domains.

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
Affected:= 9.0.0= 9.5.0= 10.0.0= 10.5.0= 10.5.1= 10.6.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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 the installed version of Cisco Prime Collaboration Assurance
    Log into the Cisco Prime Collaboration Assurance web interface and navigate to the About page, or run 'show version' via the CLI to retrieve the installed software version.
    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, or 10.6.0.
  2. Confirm multi-tenant feature is enabled
    Access the Administration or Tenant Management section in the web UI to verify if multiple tenant domains are configured and active in the environment.
    Affected if Multi-tenant isolation is configured and the product version is among the affected versions listed.
  3. Audit existing administrative accounts for unauthorized creations
    Navigate to User Administration or Administration > Users in the web UI and review the list of administrative accounts, noting creation dates and owners.
    Affected if Unexpected administrative accounts exist that were not created by known authorized administrators.
  4. Review access logs for cross-tenant data access attempts
    Examine system logs or audit logs for requests that access tenant data outside the user's assigned tenant domain, looking for unusual tenant_id parameters in URLs.
    Affected if Logs show authenticated users accessing data from tenant domains they are not authorized to view.

The environment is affected if the installed Cisco Prime Collaboration Assurance version is 9.0.0, 9.5.0, 10.0.0, 10.5.0, 10.5.1, or 10.6.0 and multi-tenant isolation is in use, with evidence of unauthorized admin account creation or cross-tenant data access.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Cisco Prime Collaboration Assurance version 10.5.1.53684-1 or later to obtain the vendor patch. Until patched, monitor for unauthorized administrative account creation and restrict user access to only necessary tenant domains.

Recommended fix High confidence

10.5.1.53684-1 or later

  1. 1. Back up the current Cisco Prime Collaboration Assurance configuration and data
  2. 2. Download Cisco Prime Collaboration Assurance version 10.5.1.53684-1 or later from Cisco's official download site (tools.cisco.com)
  3. 3. Review Cisco's upgrade documentation for Prime Collaboration Assurance 10.5.1
  4. 4. Execute the upgrade following Cisco's standard upgrade procedure for the specific platform
  5. 5. After upgrade, verify the web framework properly enforces tenant domain access restrictions
  6. 6. Confirm that authenticated users can no longer bypass access controls to create administrative accounts or read data from arbitrary tenant domains
Caveat Test upgrade in non-production environment first; review Cisco release notes for any compatibility or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prime Collaboration Assurance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2015-4304 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