dbcve.org
Prime Collaboration ProvisioningApplication · Cisco

CVE-2015-4307

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 Provisioning before 11.0 allows remote authenticated users to bypass intended access restrictions and create administrative accounts via a crafted URL, aka Bug ID CSCut64111.

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 Provisioning before version 11.0 contains an authentication bypass vulnerability that allows any remote authenticated user to create administrative accounts by manipulating URLs. This vertical privilege escalation enables a standard user to gain full administrative control over the system.

MitigationUpgrade Cisco Prime Collaboration Provisioning to version 11.0 or later. Until upgraded, restrict network access to the provisioning interface to trusted users only and monitor for unauthorized administrative account creation.

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
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 installed version
    Log into the Cisco Prime Collaboration Provisioning web interface and navigate to Administration > Software Updates > Installed Software, or use the CLI command 'show version' via SSH/Telnet to determine the exact software version.
    Affected if The installed version is 9.0.0, 9.5.0, 10.0.0, 10.5.0, 10.5.1, or 10.6.0 (any version before 11.0).
  2. Verify web interface is exposed
    Confirm whether the Cisco Prime Collaboration Provisioning web interface (typically ports 443 or 8080) is accessible from network segments outside your trusted administrative network.
    Affected if The provisioning web interface is accessible from untrusted or external networks.
  3. Review user accounts for unauthorized admin creation
    Navigate to Administration > Users > User Management in the web UI and examine all accounts with Administrative role. Cross-reference creation timestamps and creators against known legitimate administrators.
    Affected if There are administrative accounts present that were created by standard users or at times inconsistent with known admin activity.
  4. Audit access logs for URL manipulation patterns
    Review server access logs and application logs for suspicious requests that manipulate URL paths, specifically look for POST/GET requests to admin creation endpoints using non-admin credentials.
    Affected if Logs show non-administrative users accessing admin-level URLs or attempting to create administrative accounts.

You are affected if your Cisco Prime Collaboration Provisioning version is 9.0.0 through 10.6.0 and the web interface is accessible, particularly from untrusted networks, as an authenticated user could have created unauthorized admin accounts via URL manipulation.

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 Cisco Prime Collaboration Provisioning to version 11.0 or later. Until upgraded, restrict network access to the provisioning interface to trusted users only and monitor for unauthorized administrative account creation.

Recommended fix High confidence

Cisco Prime Collaboration Provisioning 11.0 or later

  1. Review Cisco Prime Collaboration Provisioning 11.0 release notes and upgrade guide for version-specific requirements
  2. Perform a complete backup of the current installation including database and configuration
  3. Test the upgrade in a non-production environment before deploying to production
  4. Download Cisco Prime Collaboration Provisioning version 11.0 or later from Cisco.com
  5. Execute the upgrade following Cisco's documented upgrade procedure
  6. Verify the upgrade was successful by checking the version number
  7. Confirm the vulnerability is resolved by testing that the crafted URL no longer allows privilege escalation
Caveat Review Cisco release notes for 11.0 - major version upgrades may include feature changes, database migrations, and compatibility considerations with integrated systems

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

Fix this in Prime Collaboration Provisioning Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4307 — 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-4307 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