dbcve.org
Unified Customer Voice PortalApplication · Cisco

CVE-2013-1222

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 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 launch arbitrary custom web applications via a crafted (1) HTTP or (2) HTTPS request, aka Bug ID CSCub38379.

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 Tomcat Web Management interface in Cisco CVP before version 9.0.1 ES 11 contains a configuration vulnerability that allows unauthenticated remote attackers to deploy arbitrary custom web applications. The Tomcat components are not properly secured, permitting attackers to send crafted HTTP/HTTPS requests that can load malicious web applications into the server context.

MitigationUpgrade Cisco CVP to version 9.0.1 ES 11 or later. If immediate upgrade is not possible, disable or restrict access to the Tomcat Web Management interface through network segmentation or firewall rules to prevent unauthorized deployment of web applications.

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

AV:N/AC:L/Au:N/C:N/I:C/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. Identify Cisco CVP installation
    Check if Cisco Unified Customer Voice Portal is installed on the system. Look for CVP installation directories or services (typically in C:\CVP or C:\Program Files\Cisco\CVP on Windows).
    Affected if Cisco CVP software is found on the system
  2. Check CVP version against affected range
    Locate the installed CVP version. Check the version against these affected versions: 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). Compare your installed version number to these listed versions.
    Affected if Installed version matches or falls within the listed affected versions
  3. Verify Tomcat Web Management interface accessibility
    Check if the Tomcat Web Management interface (typically accessible via /manager/html or /admin on ports 8080 or 8443) is exposed and reachable from the network. Use a web browser or curl to attempt access to these paths on the CVP server.
    Affected if Tomcat manager or admin interfaces are accessible without authentication
  4. Inspect Tomcat configuration for security
    Examine the Tomcat server.xml and context.xml configuration files in the CVP installation (typically in conf/ directory under the Tomcat folder). Check for unrestricted access to manager and admin applications without proper authentication constraints.
    Affected if Tomcat manager/admin applications are configured without authentication or IP restrictions

A user is affected if Cisco CVP is installed with a version matching the affected list AND the Tomcat Web Management interface is accessible without authentication.

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 to version 9.0.1 ES 11 or later. If immediate upgrade is not possible, disable or restrict access to the Tomcat Web Management interface through network segmentation or firewall rules to prevent unauthorized deployment of web applications.

Fix this in Unified Customer Voice Portal 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-2013-1222 — 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-1222 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