dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2011-0378

HIGH · 8.3 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 →
88/100
Remediation priority · High
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 XML-RPC implementation on Cisco TelePresence endpoint devices with software 1.2.x through 1.5.x allows remote attackers to execute arbitrary commands via a TCP request, related to a "command injection vulnerability," aka Bug ID CSCtb52587.

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 XML-RPC implementation on Cisco TelePresence endpoint devices running software versions 1.2.x through 1.5.x contains a command injection vulnerability that allows remote attackers to execute arbitrary commands via specially crafted TCP requests.

MitigationUpgrade Cisco TelePresence endpoint devices to a patched software version beyond 1.5.x. If immediate patching is not possible, disable XML-RPC services or implement network segmentation to restrict access to trusted sources only.

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 System SoftwareApplication
Affected:= 1.2.3= 1.3.2= 1.4.7= 1.5.1= 1.5.3= 1.5.10= 1.5.11= 1.5.12= 1.5.13
Telepresence System 1000Hardware / appliance
Affected:all versions
Telepresence System 1100Hardware / appliance
Affected:all versions
Telepresence System 3000Hardware / appliance
Affected:all versions
Telepresence System 1300 SeriesHardware / appliance
Affected:all versions
Telepresence System 3200 SeriesHardware / appliance
Affected:all versions
Telepresence System 500 SeriesHardware / appliance
Affected:all versions

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
Adjacent
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

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 Cisco TelePresence model
    Log into the device CLI or web interface and retrieve the system model information. Look for model numbers: System 1000, 1100, 3000, 1300, 3200, or 500 Series.
    Affected if The device is any of these model series (all versions are affected).
  2. Determine the software version
    Access the device through CLI (show version) or web interface and record the software version number.
    Affected if The version falls within 1.2.x through 1.5.x range, or specifically matches: 1.2.3, 1.3.2, 1.4.7, 1.5.1, 1.5.3, 1.5.10, 1.5.11, 1.5.12, or 1.5.13.
  3. Verify XML-RPC service status
    Check if the XML-RPC service is enabled and listening on the device. Use 'show service' or check port 80/443 availability. Consult device documentation for XML-RPC specific diagnostic commands.
    Affected if XML-RPC service is enabled and accessible on the network.
  4. Assess network exposure of XML-RPC
    Review firewall rules, ACLs, and network topology to determine if the XML-RPC service is exposed to untrusted networks or the internet.
    Affected if The XML-RPC service is reachable from untrusted networks or directly from the internet.

The environment is affected if the device is a TelePresence System 1000/1100/3000/1300/3200/500 (any version) or runs software 1.2.x through 1.5.x, and XML-RPC is enabled and accessible from an untrusted network.

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

Upgrade Cisco TelePresence endpoint devices to a patched software version beyond 1.5.x. If immediate patching is not possible, disable XML-RPC services or implement network segmentation to restrict access to trusted sources only.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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