dbcve.org
Unified Ip Interactive Voice ResponseHardware / appliance · Cisco

CVE-2011-3315

HIGH · 7.8 CVSS v2.0 Published 2011-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Directory traversal vulnerability in Cisco Unified Communications Manager (CUCM) 5.x and 6.x before 6.1(5)SU2, 7.x before 7.1(5b)SU2, and 8.x before 8.0(3), and Cisco Unified Contact Center Express (aka Unified CCX or UCCX) and Cisco Unified IP Interactive Voice Response (Unified IP-IVR) before 6.0(1)SR1ES8, 7.0(x) before 7.0(2)ES1, 8.0(x) through 8.0(2)SU3, and 8.5(x) before 8.5(1)SU2, allows remote attackers to read arbitrary files via a crafted URL, aka Bug IDs CSCth09343 and CSCts44049.

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

Directory traversal vulnerability in Cisco Unified Communications Manager and Cisco Unified Contact Center Express products allows remote unauthenticated attackers to read arbitrary files on the system via crafted URL requests containing path traversal sequences (e.g., ../../../'). The vulnerability exists in the web interface components of CUCM versions 5.x through 8.x before specified patch levels and UCCX/Unified IP-IVR versions before 8.5(1)SU2.

MitigationApply the vendor-supplied software updates: upgrade CUCM to 6.1(5)SU2, 7.1(5b)SU2, or 8.0(3) and later; upgrade UCCX/Unified IP-IVR to 6.0(1)SR1ES8, 7.0(2)ES1, 8.0(2)SU3, or 8.5(1)SU2 or later. Implement web application firewall rules to block path traversal patterns as an interim control.

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 Ip Interactive Voice ResponseHardware / appliance
Affected:all versions
Unified Ip IvrApplication
Affected:= 6.0\(1\)= 7.0\(1\)= 7.0\(2\)= 8.0\(1\)= 8.0\(2\)= 8.5\(1\)
Unified Communications ManagerApplication
Affected:= 5.0= 5.1= 5.1\(1\)= 5.1\(1b\)= 5.1\(1c\)= 5.1\(2\)= 5.1\(2a\)= 5.1\(2b\)= 5.1\(3\)= 5.1\(3a\)= 5.1\(3c\)= 5.1\(3d\)

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 installed Cisco product
    Run 'show version' on the device CLI or check the admin web interface for the product name (CUCM, UCCX, or Unified IP-IVR)
    Affected if Product is Cisco Unified Communications Manager, Unified IP-IVR, or Unified IP Interactive Voice Response
  2. Determine CUCM version
    Check the version via CLI command 'show version' or the web admin interface under 'Help > About'. Affected versions are 5.0, 5.1, 5.1(1), 5.1(1b), 5.1(1c), 5.1(2), 5.1(2a), 5.1(2b), 5.1(3), 5.1(3a), 5.1(3c), 5.1(3d)
    Affected if Installed CUCM version matches any of the affected versions listed in the CVE and is before patches 6.1(5)SU2, 7.1(5b)SU2, or 8.0(3)
  3. Determine Unified IP-IVR version
    Check the version via CLI or web admin interface. Affected versions are 6.0(1), 7.0(1), 7.0(2), 8.0(1), 8.0(2), 8.5(1)
    Affected if Installed Unified IP-IVR version matches any of the affected versions and is before 8.5(1)SU2
  4. Confirm web interface is enabled
    Verify the Cisco Tomcat web service is running by checking the service status via CLI command 'utils service list' or by confirming port 443/https is open and responding
    Affected if The web interface (Cisco Tomcat or similar web service) is enabled and exposed on the device
  5. Test for path traversal vulnerability
    Send a crafted HTTP GET request to the web interface containing path traversal sequences such as '/..%2F..%2F..%2Fetc/passwd' or '/..\..\..\windows\system32\config\sam' (URL-encoded or raw)
    Affected if The server returns file contents from outside the web root directory, indicating successful directory traversal

The environment is affected if either CUCM (versions 5.x-8.x before specified patch levels) or Unified IP-IVR (versions 6.0(1) through 8.5(1) before 8.5(1)SU2) is installed with the web interface enabled, and the system responds to path traversal URL patterns.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied software updates: upgrade CUCM to 6.1(5)SU2, 7.1(5b)SU2, or 8.0(3) and later; upgrade UCCX/Unified IP-IVR to 6.0(1)SR1ES8, 7.0(2)ES1, 8.0(2)SU3, or 8.5(1)SU2 or later. Implement web application firewall rules to block path traversal patterns as an interim control.

Fix this in Unified Ip Interactive Voice Response Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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