dbcve.org
Unified Customer Voice PortalApplication · Cisco

CVE-2018-0086

HIGH · 8.6 CVSS v3.0 Published 2018-01-18
Fix available
A fix is available. Upgrade to after 11.5 or later.
See remediation →
95/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 application server of the Cisco Unified Customer Voice Portal (CVP) could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on the affected device. The vulnerability is due to malformed SIP INVITE traffic received on the CVP during communications with the Cisco Virtualized Voice Browser (VVB). An attacker could exploit this vulnerability by sending malformed SIP INVITE traffic to the targeted appliance. An exploit could allow the attacker to impact the availability of services and data on the device, causing a DoS condition. This vulnerability affects Cisco Unified CVP running any software release prior to 11.6(1). Cisco Bug IDs: CSCve85840.

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

A denial of service vulnerability exists in the application server of Cisco Unified Customer Voice Portal (CVP) where malformed SIP INVITE traffic received from the Cisco Virtualized Voice Browser (VVB) can cause the service to become unavailable. An unauthenticated remote attacker can exploit this by sending specially crafted SIP INVITE messages to the targeted appliance, impacting the availability of voice portal services.

MitigationUpgrade Cisco Unified CVP to version 11.6(1) or later to remediate this vulnerability. Until the upgrade is completed, consider implementing network-level filtering to block malformed SIP traffic from untrusted sources.

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
Unified Customer Voice PortalApplication
Affected:<= 11.5

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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 CVP version
    Access the CVP server via admin console or run 'show version' command in CVP OAMP/Operations Console. Navigate to System > Server > [select server] to view the installed CVP version.
    Affected if The installed version is 11.5 or earlier (any version <= 11.5)
  2. Verify SIP service is enabled
    Check CVP Service Manager or the Call Server configuration to confirm the SIP service (Call Server) is running and enabled. Look for SIP listener status in the CVP configuration.
    Affected if The SIP Call Server service is enabled and running - this is required for the vulnerability to be exploitable
  3. Check network exposure to SIP traffic
    Review firewall rules or network ACLs to determine if the CVP server's SIP ports (typically UDP/TCP 5060) are accessible from untrusted or external networks. Check if VVB connectivity is from untrusted sources.
    Affected if The SIP service port is accessible from untrusted networks or directly from Cisco VVB systems without network-level filtering

A user is affected if their Cisco Unified CVP version is 11.5 or earlier AND the SIP service is exposed to network traffic from Cisco VVB or untrusted sources.

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 11.5
Interim mitigation

Upgrade Cisco Unified CVP to version 11.6(1) or later to remediate this vulnerability. Until the upgrade is completed, consider implementing network-level filtering to block malformed SIP traffic from untrusted sources.

Fix this in Unified Customer Voice Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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