Unified Customer Voice PortalApplication · Cisco

CVE-2013-1225

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
Cisco Unified Customer Voice Portal (CVP) Software before 9.0.1 ES 11 allows remote attackers to read arbitrary files via a Resource Manager (1) HTTP or (2) HTTPS request containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, aka Bug ID CSCub38366.

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

XML External Entity (XXE) injection vulnerability in Cisco CVP Resource Manager allows remote attackers to read arbitrary files by crafting XML requests with malicious external entity declarations. The vulnerability exists in both HTTP and HTTPS endpoints of the Resource Manager component.

MitigationApply Cisco CVP software version 9.0.1 ES 11 or later which patches this XXE vulnerability. As interim mitigation, restrict network access to the Resource Manager service and implement XML input validation to block external entity declarations.

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

AV:N/AC:L/Au:N/C:C/I:N/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
    Locate the Cisco Unified Customer Voice Portal installation directory or check system inventory for CVP components
    Affected if Cisco CVP Resource Manager component is installed on the system
  2. Determine CVP version
    Use the CVP administrative interface, check installed packages, or query the Resource Manager service version endpoint if available
    Affected if The installed version matches any of: 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)
  3. Verify Resource Manager HTTP endpoint is exposed
    Attempt to access the Resource Manager HTTP service endpoint (typically port 8080 or 8000) via curl or browser
    Affected if The HTTP endpoint responds to requests, indicating Resource Manager is network-accessible
  4. Verify Resource Manager HTTPS endpoint is exposed
    Attempt to access the Resource Manager HTTPS service endpoint (typically port 8443) via curl or browser
    Affected if The HTTPS endpoint responds to requests, indicating Resource Manager is network-accessible
  5. Confirm XML requests are accepted
    Send a test XML request to the Resource Manager endpoint to verify it processes XML input
    Affected if The endpoint accepts and processes XML requests without rejecting external entity declarations

If Cisco CVP with Resource Manager is installed and the version falls within 3.0 through 9.0(1), and the HTTP/HTTPS endpoints are accessible, the environment is vulnerable to XXE injection via crafted XML requests.

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

Apply Cisco CVP software version 9.0.1 ES 11 or later which patches this XXE vulnerability. As interim mitigation, restrict network access to the Resource Manager service and implement XML input validation to block external entity declarations.

Fix this in Unified Customer Voice Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1225 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