Telepresence Multipoint Switch SoftwareApplication · Cisco
CVE-2011-0384
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 · uneditedThe Java Servlet framework on Cisco TelePresence Multipoint Switch (CTMS) devices with software 1.0.x, 1.1.x, 1.5.x, and 1.6.x does not require administrative authentication for unspecified actions, which allows remote attackers to execute arbitrary code via a crafted request, aka Bug ID CSCtf01253.
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 confidenceThe Java Servlet framework in Cisco TelePresence Multipoint Switch (CTMS) devices fails to enforce administrative authentication for certain actions, allowing unauthenticated remote attackers to send crafted requests that execute arbitrary code on the affected device.
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 Multipoint Switch SoftwareApplication
= 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
all versionsCVSS 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
- Complete
- Availability
- Complete
AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device as Cisco TelePresence Multipoint SwitchLog into the device CLI and run 'show version' or check the web management interface header to confirm the device model is CTMS or Cisco TelePresence Multipoint SwitchAffected if The device is identified as a Cisco TelePresence Multipoint Switch (CTMS)
-
Determine the software versionRun 'show version' in the CLI or check the web interface under Administration > Software Version to retrieve the exact installed version numberAffected if The installed version matches any of these: 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, or 1.6.0, or if the version cannot be determined but the hardware is CTMS (which affects all versions)
-
Verify Java Servlet management interface exposureCheck if TCP ports used by the Java Servlet container (typically 80, 443, or custom web service ports) are listening and accessible from untrusted networks by running 'show ip interface brief' and reviewing firewall rules or ACLsAffected if The web management interface is reachable from outside the trusted network without authentication restrictions
-
Confirm authentication is not enforced on servlet endpointsAttempt to access common servlet paths (such as /admin, /servlet, or diagnostic endpoints) via HTTP/HTTPS without providing credentials; if the request is accepted and returns a valid response rather than an authentication prompt, the vulnerability is presentAffected if HTTP requests to servlet endpoints return valid responses without requiring login credentials
The environment is affected if the device is a Cisco TelePresence Multipoint Switch running any of the listed software versions (1.0.4.0, 1.1.x, 1.5.x, 1.6.0) or if the hardware version cannot be determined but the device is CTMS, and the management interface is network-accessible without authentication enforcement.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply Cisco software updates addressing CSCtf01253 for affected versions 1.0.x through 1.6.x; if patches are unavailable, restrict network access to management interfaces via firewall or ACLs.
Cisco TelePresence Multipoint Switch software 1.7.x or later (specific version per Cisco advisory cisco-sa-20110209-ctms)
- Check the Cisco Security Advisory cisco-sa-20110209-ctms for the specific fixed software version
- Identify the current installed version using 'show version' or 'admin show system' commands
- Obtain the fixed software image from Cisco (requires valid service contract)
- Upload the new software image to the CTMS device using the admin interface or SCP
- Perform a software upgrade following Cisco's standard upgrade procedure
- Verify the upgrade was successful and the vulnerability is patched
- Confirm administrative authentication is now required for all servlet actions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Telepresence Multipoint Switch Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0384 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-0384 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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