dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2011-1607

MEDIUM · 6.5 CVSS v2.0 Published 2011-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 (aka CUCM, formerly CallManager) 6.x before 6.1(5)su3, 7.x before 7.1(5b)su3, 8.0 before 8.0(3a)su1, and 8.5 before 8.5(1) allows remote authenticated users to upload files to arbitrary directories via a modified pathname in an upload request, aka Bug ID CSCti81603.

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's web-based file upload functionality allows authenticated remote users to manipulate upload pathnames (using '../' sequences) to write files to arbitrary directories on the system. This could enable privilege escalation or code execution if attackers can place executable content in web-accessible locations.

MitigationApply Cisco-supplied patches by upgrading to the fixed versions (6.1(5)su3, 7.1(5b)su3, 8.0(3a)su1, 8.5(1) or later). If immediate patching is not feasible, restrict administrative access to the CUCM web interface via network segmentation or VPN, and ensure strong authentication for all accounts with upload privileges.

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 Communications ManagerApplication
Affected:= 6.0= 6.1\(1\)= 6.1\(1a\)= 6.1\(1b\)= 6.1\(2\)= 6.1\(2\)su1= 6.1\(2\)su1a= 6.1\(3\)= 6.1\(3a\)= 6.1\(3b\)= 6.1\(3b\)su1= 6.1\(4\)

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 CUCM version
    Log into the CUCM Administration interface and navigate to About > Version, or run 'show version' via CLI using the admin account. Alternatively, check the Cisco Unified Reporting tool for system version information.
    Affected if The installed version matches exactly one of the following: 6.0, 6.1(1), 6.1(1a), 6.1(1b), 6.1(2), 6.1(2)su1, 6.1(2)su1a, 6.1(3), 6.1(3a), 6.1(3b), or 6.1(3b)su1.
  2. Verify web interface accessibility
    Determine if the CUCM web administration interface (typically port 8443 or 443) is reachable from network segments outside the administrative zone. Use a browser or curl to confirm HTTP/HTTPS response from the web server.
    Affected if The web interface is exposed to untrusted or less-trusted network segments.
  3. Confirm web service is running
    Check if the Cisco Tomcat web service is active by accessing the web login page or running 'utils service list' via the CUCM CLI.
    Affected if The web-based upload functionality is available (web service is running).
  4. Review web access logs for upload activity
    Access RTMT (Real Time Monitoring Tool) or review log files under /var/log/active/tomcat/logs/ for suspicious upload requests containing '../' path traversal sequences.
    Affected if Logs show file upload attempts with directory traversal patterns or unauthorized file placement.

You are affected if your installed CUCM version matches the affected list (6.0 or 6.1.x series listed) AND the web interface is accessible to users with upload privileges.

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 Cisco-supplied patches by upgrading to the fixed versions (6.1(5)su3, 7.1(5b)su3, 8.0(3a)su1, 8.5(1) or later). If immediate patching is not feasible, restrict administrative access to the CUCM web interface via network segmentation or VPN, and ensure strong authentication for all accounts with upload privileges.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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