dbcve.org
Unified Customer Voice PortalApplication · Cisco

CVE-2013-1221

HIGH · 10.0 CVSS v2.0 Published 2013-05-09
Fix available
A fix is available. Upgrade to after 9.0 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
The Tomcat Web Management feature in Cisco Unified Customer Voice Portal (CVP) Software before 9.0.1 ES 11 does not properly configure Tomcat components, which allows remote attackers to execute arbitrary code via a crafted (1) HTTP or (2) HTTPS request, aka Bug ID CSCub38384.

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

Cisco Unified Customer Voice Portal (CVP) versions before 9.0.1 ES 11 contain a misconfigured Tomcat Web Management interface that allows unauthenticated remote attackers to execute arbitrary code via specially crafted HTTP/HTTPS requests due to improper Tomcat component configuration.

MitigationUpgrade Cisco CVP Software to version 9.0.1 ES 11 or later to address the improperly configured Tomcat components.

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/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. Identify installed CVP version
    Access the CVP server and retrieve the installed version using the CVP administrative interface or by running 'show version' command in the CVP OAMP/Call Server CLI
    Affected if The installed version matches any of these: 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)
  2. Verify Tomcat Web Management interface accessibility
    Attempt to access the Tomcat management endpoints (typically /manager/html or /admin) on the CVP server via HTTP/HTTPS from an untrusted network perspective
    Affected if The Tomcat Web Management interface is accessible without authentication on ports 80, 443, 8080, or 8443
  3. Confirm Tomcat configuration exposes management interface
    Inspect the Tomcat server.xml and context.xml configuration files located in the CVP Tomcat conf directory to verify if the manager and admin applications are deployed with weak or missing access controls
    Affected if The manager and admin web applications are configured without proper authentication or are bound to accessible network interfaces without restriction

A user is affected if they are running any Cisco CVP version 9.0 or earlier (including 3.x, 4.x, 7.x, 8.x) and the Tomcat Web Management interface is exposed and accessible without authentication on the network.

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 a release after 9.0
Interim mitigation

Upgrade Cisco CVP Software to version 9.0.1 ES 11 or later to address the improperly configured Tomcat components.

Recommended fix High confidence

9.0.1 ES 11 or later

  1. 1. Verify the current Cisco Unified CVP version by accessing the CVP Operations Console or running 'show version' on the device
  2. 2. If running version 9.0(1) or earlier, or versions 3.0, 3.6(10), or 4.0, the system is vulnerable
  3. 3. Download Cisco Unified CVP version 9.0.1 ES 11 or later from the Cisco Software Download Center (tools.cisco.com)
  4. 4. Review Cisco release notes and upgrade documentation for CVP 9.0.1
  5. 5. Perform a backup of the current CVP configuration and database
  6. 6. Follow Cisco's standard upgrade procedure for Unified CVP, which typically involves upgrading the Call Server, Reporting Server, and VoiceXML servers in the correct order
  7. 7. After upgrade, verify that the Tomcat Web Management interface is properly secured (disable default accounts, restrict access to management ports, enable proper authentication)
  8. 8. Confirm the new version is installed by checking 'show version' output
Caveat Standard CVP upgrade precautions apply - schedule maintenance window, backup configuration, test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unified Customer Voice Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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