Unified Customer Voice PortalApplication · Cisco
CVE-2018-0139
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 · uneditedA vulnerability in the Interactive Voice Response (IVR) management connection interface for Cisco Unified Customer Voice Portal (CVP) could allow an unauthenticated, remote attacker to cause the IVR connection to disconnect, creating a system-wide denial of service (DoS) condition. The vulnerability is due to improper handling of a TCP connection request when the IVR connection is already established. An attacker could exploit this vulnerability by initiating a crafted connection to the IP address of the targeted CVP device. An exploit could allow the attacker to disconnect the IVR to CVP connection, creating a DoS condition that prevents the CVP from accepting new, incoming calls while the IVR automatically attempts to re-establish the connection to the CVP. This vulnerability affects Cisco Unified Customer Voice Portal (CVP) Software Release 11.5(1). Cisco Bug IDs: CSCve70560.
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 confidenceA vulnerability in the IVR management connection interface for Cisco Unified CVP allows an unauthenticated remote attacker to cause denial of service by sending crafted TCP connection requests. The improper handling of these requests when an IVR connection is already established causes the IVR-to-CVP connection to disconnect, preventing the CVP from accepting new incoming calls.
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
= 11.5\(1\)= 11.6CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Unified CVP installationUse the command 'show version' on the CVP server or check the application version through the CVP Operations Console. On Windows, check Add/Remove Programs or the CVP installation directory for version files.Affected if The installed version matches 11.5(1) or 11.6 exactly.
-
Verify IVR management interface exposureCheck network configuration to determine if TCP port 7000 (default IVR management port) or the CVP management interface is accessible from untrusted networks. Review firewall rules and access control lists.Affected if The IVR management interface is exposed to network segments where untrusted users could send TCP connection requests.
-
Review IVR connection statusMonitor the CVP server logs and use the CVP Operations Console to check for unexpected IVR disconnects or connection failures. Look for patterns of connection drops following external TCP attempts.Affected if IVR-to-CVP connections are disconnecting unexpectedly without other apparent causes.
-
Check for vulnerability indicatorsExamine CVP system logs for error messages related to TCP connection handling failures or IVR connection drops. Compare logs around the time of incidents.Affected if Logs show connection handling errors or IVR disconnects correlate with external TCP connection attempts to the management interface.
A user is affected if they are running Cisco Unified CVP version 11.5(1) or 11.6 and the IVR management interface is network-accessible, leading to potential IVR connection disconnections.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Cisco patch for CSCve70560 (Cisco CVP 11.5(1) software update). If immediate patching is not possible, consider network segmentation or firewall rules to restrict unauthorized access to the CVP management interface.
Fix this in Unified Customer Voice Portal
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-0139 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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