dbcve.org
Prime Collaboration AssuranceApplication · Cisco

CVE-2019-1662

CRITICAL · 9.1 CVSS v3.0 Published 2019-02-21
Fix available
A fix is available. Upgrade to 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 Quality of Voice Reporting (QOVR) service of Cisco Prime Collaboration Assurance (PCA) Software could allow an unauthenticated, remote attacker to access the system as a valid user. The vulnerability is due to insufficient authentication controls. An attacker could exploit this vulnerability by connecting to the QOVR service with a valid username. A successful exploit could allow the attacker to perform actions with the privileges of the user that is used for access. This vulnerability affects Cisco PCA Software Releases prior to 12.1 SP2.

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 Quality of Voice Reporting (QOVR) service in Cisco Prime Collaboration Assurance (PCA) Software contains insufficient authentication controls, allowing an unauthenticated remote attacker to connect to the service using any valid username and gain that user's privileges on the system.

MitigationUpgrade to Cisco PCA Software Release 12.1 SP2 or later to obtain the patched authentication controls in the QOVR service.

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:< 12.1= 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
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cisco PCA installation
    Identify if Cisco Prime Collaboration Assurance software is installed on the system
    Affected if The software is not present on the system, the vulnerability does not apply
  2. Check installed PCA version
    Retrieve the installed version of Cisco Prime Collaboration Assurance and compare it to the affected ranges: versions less than 12.1, or exactly version 12.1
    Affected if The installed version is 12.1 or any version earlier than 12.1
  3. Confirm QOVR service status
    Determine whether the Quality of Voice Reporting (QOVR) service is running or enabled on the PCA installation
    Affected if The QOVR service is not running or not present, the exploitation vector is unavailable
  4. Inspect QOVR authentication configuration
    Examine the QOVR service configuration files or settings for authentication controls - verify whether any valid username can authenticate without proper credential validation
    Affected if The QOVR service allows authentication with any valid username without requiring proper password verification, indicating the vulnerability is present

The environment is affected if Cisco Prime Collaboration Assurance is installed with a version less than 12.1 or equal to 12.1, and the QOVR service is running with weak authentication controls that accept any valid username.

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
Upgrade available Upgrade to 12.1 or later
Fixed in 12.1
Interim mitigation

Upgrade to Cisco PCA Software Release 12.1 SP2 or later to obtain the patched authentication controls in the QOVR service.

Recommended fix High confidence

Cisco Prime Collaboration Assurance 12.1 SP2 or later

  1. 1. Identify current Cisco Prime Collaboration Assurance version using the admin interface or CLI command 'show version'
  2. 2. Plan maintenance window as upgrade will require service restart
  3. 3. Backup current PCA configuration and database
  4. 4. Download Cisco PCA 12.1 SP2 or later from Cisco Software Download center (requires valid CCO account)
  5. 5. Access PCA admin interface and navigate to Administration > Software Updates
  6. 6. Upload the upgrade package and initiate installation
  7. 7. After upgrade completes, verify QOVR service is running
  8. 8. Confirm version upgrade successful with 'show version' command showing 12.1 SP2 or later
Caveat Upgrade requires downtime; ensure backup of configuration before proceeding; may require re-validation of integrations

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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