dbcve.org
Prime CollaborationApplication · Cisco

CVE-2018-0320

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-07
Fix available
A fix is available. Upgrade to after 12.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability in the web framework code of Cisco Prime Collaboration Provisioning (PCP) could allow an unauthenticated, remote attacker to execute arbitrary SQL queries. The vulnerability is due to a lack of proper validation on user-supplied input in SQL queries. An attacker could exploit this vulnerability by sending crafted URLs that contain malicious SQL statements to the affected application. This vulnerability affects Cisco Prime Collaboration Provisioning (PCP) Releases 12.1 and prior. Cisco Bug IDs: CSCvd61754.

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

Unauthenticated SQL injection in Cisco Prime Collaboration Provisioning web framework allows remote attackers to execute arbitrary SQL queries via crafted URLs containing malicious SQL statements. The vulnerability stems from lack of proper input validation on user-supplied parameters in SQL queries.

MitigationApply Cisco's patch for CSCvd61754 or upgrade to a fixed release beyond 12.1. If immediate patching is not possible, deploy WAF rules to detect and block SQL injection attempts in HTTP 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 CollaborationApplication
Affected:<= 12.1
Prime Collaboration ProvisioningApplication
Affected:<= 12.1

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 if Cisco Prime Collaboration is installed
    Check for the presence of Cisco Prime Collaboration installation directories or use system inventory tools. Common paths may include /opt/cisco/pcp or similar installation directories. Look for the 'prime' or 'cisco' application components.
    Affected if The product is found on the system
  2. Determine the installed version
    Locate the version file or use CLI commands such as 'show version' within the Prime Collaboration admin interface, or check the WAR files under the application deployment directory for version manifests.
    Affected if The installed version is 12.1 or earlier (12.1, 11.x, 10.x, etc.)
  3. Verify the web interface is accessible
    Check if the Cisco Prime Collaboration Provisioning web interface (typically on ports 443, 8443, or 8080) is exposed and reachable from the network. Attempt to access the login or API endpoints.
    Affected if The web interface is accessible externally or on untrusted networks
  4. Review web server access logs for SQL injection patterns
    Examine HTTP access logs (typically in /opt/cisco/pcp/tomcat/logs or similar) for suspicious URL patterns containing SQL keywords like UNION, SELECT, INSERT, OR 1=1, or common SQL injection payloads in query parameters.
    Affected if SQL injection attempt patterns are found in the logs targeting this application

The environment is affected if Cisco Prime Collaboration or Cisco Prime Collaboration Provisioning version 12.1 or earlier is installed and the web interface is accessible, with potential SQL injection indicators visible in web logs.

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.

From vendor data
Upgrade available Upgrade to a release after 12.1
Interim mitigation

Apply Cisco's patch for CSCvd61754 or upgrade to a fixed release beyond 12.1. If immediate patching is not possible, deploy WAF rules to detect and block SQL injection attempts in HTTP requests.

Fix this in Prime Collaboration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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