Telepresence ManagerApplication · Cisco

CVE-2011-0380

HIGH · 7.5 CVSS v2.0 Published 2011-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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 TelePresence Manager 1.2.x through 1.6.x allows remote attackers to bypass authentication and invoke arbitrary methods via a malformed SOAP request, aka Bug ID CSCtc59562.

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 TelePresence Manager versions 1.2.x through 1.6.x contains an authentication bypass vulnerability in its SOAP-based web service interface. Attackers can send malformed SOAP requests to bypass authentication and invoke arbitrary methods on the TelePresence management system, potentially gaining full control over conference management functions.

MitigationApply the vendor patch from Cisco for Bug ID CSCtc59562, which upgrades to a fixed version. If patching is not immediately possible, restrict network access to the TelePresence Manager management interface using firewall rules or network segmentation to prevent unauthorized SOAP requests.

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
Telepresence ManagerApplication
Affected:= 1.2.0.0= 1.3.2= 1.4.0= 1.5.1= 1.5.2= 1.6.0= 1.6.2= 1.6.3= 1.6.5

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

AV:N/AC:L/Au:N/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 the installed Cisco TelePresence Manager version
    Access the TelePresence Manager administrative web interface and navigate to the About or System Information page, or run 'show version' via CLI if available
    Affected if The displayed version matches 1.2.0.0, 1.3.2, 1.4.0, 1.5.1, 1.5.2, 1.6.0, 1.6.2, 1.6.3, or 1.6.5, or falls within the 1.2.x through 1.6.x range
  2. Confirm the SOAP-based web service interface is accessible
    Check if port 8080 or the HTTPS management port is open and responding on the TelePresence Manager server using a port scanner or netstat command
    Affected if The SOAP web service port is exposed and accepts connections from unauthorized networks
  3. Review management interface access controls
    Examine the network configuration or firewall rules to determine if the TelePresence Manager management interface is accessible from untrusted networks
    Affected if The management interface is reachable from outside the trusted network without filtering
  4. Inspect logs for malformed SOAP requests
    Review TelePresence Manager application logs, typically found in the logs directory or via the web interface log viewer, for entries containing malformed SOAP envelopes or unexpected method names
    Affected if Logs show SOAP requests with missing authentication headers or attempts to invoke unauthorized methods

A user is affected if their TelePresence Manager version falls within 1.2.x through 1.6.x and the SOAP-based management interface is network-accessible to untrusted users.

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 patch from Cisco for Bug ID CSCtc59562, which upgrades to a fixed version. If patching is not immediately possible, restrict network access to the TelePresence Manager management interface using firewall rules or network segmentation to prevent unauthorized SOAP requests.

Fix this in Telepresence Manager 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 help mitigating

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-2011-0380 — 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-2011-0380 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