dbcve.org
Unified Customer Voice PortalApplication · Cisco

CVE-2013-1220

HIGH · 7.8 CVSS v2.0 Published 2013-05-09
Fix available
A fix is available. Upgrade to after 9.0 or later.
See remediation →
87/100
Remediation priority · High
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
The CallServer component in Cisco Unified Customer Voice Portal (CVP) Software before 9.0.1 ES 11 allows remote attackers to cause a denial of service (call-acceptance outage) via malformed SIP INVITE messages, aka Bug ID CSCua65148.

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 CallServer component in Cisco Unified Customer Voice Portal (CVP) Software contains a denial-of-service vulnerability where malformed SIP INVITE messages can cause the call-acceptance system to fail, preventing legitimate calls from being processed.

MitigationUpgrade Cisco CVP Software to version 9.0.1 ES 11 or later to patch this vulnerability. In production environments, validate SIP call flows after patching.

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:<= 9.0\(1\)= 3.0= 3.6\(10\)= 4.0= 4.0\(2\)= 4.1= 7.0= 7.0\(2\)= 8.0\(1\)= 8.5\(1\)= 9.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
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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. Confirm Cisco CVP installation
    Locate Cisco Unified Customer Voice Portal software on the system. Check for CVP installation directories or use system inventory tools to identify if CVP components are present.
    Affected if CVP software is not installed on the system, the system is not affected.
  2. Identify CVP version
    Retrieve the installed version of Cisco Unified Customer Voice Portal. This is typically found in the CVP software management console, registry, or via command-line tools provided by CVP (such as 'opmnctl status' or similar CVP-specific commands).
    Affected if The installed version matches one of the following: 3.0, 3.6(10), 4.0, 4.0(2), 4.1, 7.0, 7.0(2), 8.0(1), 8.5(1), 9.0, or any version <= 9.0(1). If the version is unknown or not in this list, compare against the affected ranges.
  3. Verify CallServer component is active
    Check the status of the CallServer component within the CVP architecture. This can be done via the CVP OAMP console, Operations console, or by querying the CVP service status.
    Affected if The CallServer component is running and processing calls. If CallServer is disabled or not in use, the vulnerability is not exploitable in the current configuration.
  4. Confirm SIP handling is enabled
    Examine the CVP CallServer configuration to determine if SIP (Session Initiation Protocol) call handling is enabled. Check SIP-related configuration files or the CVP call routing configuration for SIP trunk or SIPleg definitions.
    Affected if SIP is enabled and the CallServer is configured to accept SIP INVITE messages. The vulnerability requires SIP to be active for the malformed INVITE to trigger the DoS condition.

The system is affected if Cisco Unified Customer Voice Portal is installed with an affected version (3.0, 3.6(10), 4.0, 4.0(2), 4.1, 7.0, 7.0(2), 8.0(1), 8.5(1, or 9.0, including <=9.0(1)) and the CallServer component with SIP handling is enabled and processing calls.

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

Upgrade Cisco CVP Software to version 9.0.1 ES 11 or later to patch this vulnerability. In production environments, validate SIP call flows after patching.

Fix this in Unified Customer Voice Portal 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 the upgrade done

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-2013-1220 — 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-2013-1220 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