Telepresence ManagerApplication · Cisco
CVE-2011-0381
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 · uneditedCisco TelePresence Manager 1.2.x through 1.6.x allows remote attackers to perform unspecified actions and consequently execute arbitrary code via a crafted request to the Java RMI interface, related to a "command injection vulnerability," aka Bug ID CSCtf97085.
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 confidenceCommand injection vulnerability in Cisco TelePresence Manager's Java RMI interface allows remote attackers to execute arbitrary code via crafted requests. The flaw affects versions 1.2.x through 1.6.x and is rated critical due to the ability to execute arbitrary code without authentication.
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
= 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.5CVSS 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 installed Cisco TelePresence Manager versionLog into the Cisco TelePresence Manager administration console or check the software version via CLI command 'show version' or through the management interface under System > AboutAffected if The installed version matches 1.2.x, 1.3.x, 1.4.x, 1.5.x, or 1.6.x (specifically 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)
-
Verify Java RMI interface is enabledAccess the Cisco TelePresence Manager configuration settings and check whether the Java RMI service is enabled under Services or Network settingsAffected if Java RMI interface is listed as enabled or active in the configuration
-
Confirm RMI port is listeningRun 'netstat -an | grep -E "1099|1098"' or use a port scanner to check if the default Java RMI ports (1099/1098) or the configured RMI port is open and listening on the management interfaceAffected if The RMI port is shown as LISTENING on any interface
-
Check network exposure of RMI serviceReview firewall rules or access control lists to determine if the RMI port is accessible from networks other than localhost or trusted management subnetsAffected if The RMI port is accessible from untrusted networks or the internet
You are affected if the installed Cisco TelePresence Manager version is 1.2.x through 1.6.x AND the Java RMI interface is enabled and exposed on the network.
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.
From vendor dataApply vendor patches or upgrade to a Cisco-supported version beyond 1.6.x. If patching is not immediately possible, restrict network access to the RMI interface via firewall rules or network segmentation.
Fix this in Telepresence Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2011-0381 — 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-0381 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