dbcve.org
Telepresence Recording Server SoftwareApplication · Cisco

CVE-2011-0388

HIGH · 7.8 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 →
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 TelePresence Recording Server devices with software 1.6.x and Cisco TelePresence Multipoint Switch (CTMS) devices with software 1.0.x, 1.1.x, 1.5.x, and 1.6.x do not properly restrict remote access to the Java servlet RMI interface, which allows remote attackers to cause a denial of service (memory consumption and web outage) via multiple crafted requests, aka Bug IDs CSCtg35830 and CSCtg35825.

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 vulnerability exists in the Java servlet RMI interface of Cisco TelePresence Recording Server (1.6.x) and Cisco TelePresence Multipoint Switch (1.0.x, 1.1.x, 1.5.x, 1.6.x) which lacks proper remote access restrictions. Attackers can send multiple crafted requests to cause memory exhaustion and web service outage.

MitigationRestrict network access to the RMI interface via firewall rules or upgrade to a patched Cisco software version if available. Given this is a 2011 CVE affecting end-of-life products, network segmentation is the primary mitigation.

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 Recording Server SoftwareApplication
Affected:= 1.6.1= 1.6.2= 1.6.3
Telepresence Recording ServerHardware / appliance
Affected:all versions
Telepresence Multipoint Switch SoftwareApplication
Affected:= 1.0.4.0= 1.1.0= 1.1.1= 1.1.2= 1.5.0= 1.5.1= 1.5.2= 1.5.3= 1.5.4= 1.5.5= 1.5.6= 1.6.0
Telepresence Multipoint SwitchHardware / 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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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 installed product
    Locate the Cisco TelePresence device and determine whether it is running Recording Server or Multipoint Switch software. Use the device management interface, CLI, or system information page to identify the product type.
    Affected if The device is a Cisco TelePresence Recording Server or Multipoint Switch
  2. Check installed version
    Access the device management interface or use the CLI command 'show version' or similar to retrieve the exact software version number. Compare against the affected version list.
    Affected if The installed version is 1.6.1, 1.6.2, or 1.6.3 for Recording Server; or 1.0.4.0, 1.1.0, 1.1.1, 1.1.2, 1.5.0 through 1.5.6, or 1.6.0 for Multipoint Switch; or any version if the product falls into the 'all versions' category for either product line
  3. Verify RMI interface accessibility
    Check if the Java servlet RMI interface is exposed by reviewing the device network configuration, firewall rules, or by attempting to access typical RMI ports (often port 1099 or configured servlet ports) from an unauthorized network location. Use 'netstat' or port scanning tools to identify open RMI-related ports.
    Affected if The RMI interface ports are accessible from untrusted networks or the internet without authentication restrictions
  4. Confirm RMI service is running
    Check device processes or services to verify the Java servlet RMI service is active. On the device, use commands like 'show process' or review the web service configuration to see if the RMI servlet is loaded and running.
    Affected if The Java servlet RMI service is actively running on the device

You are affected if you are running any version of Cisco TelePresence Recording Server or Multipoint Switch and the Java servlet RMI interface is network-accessible.

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

Restrict network access to the RMI interface via firewall rules or upgrade to a patched Cisco software version if available. Given this is a 2011 CVE affecting end-of-life products, network segmentation is the primary mitigation.

Fix this in Telepresence Recording Server Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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