Telepresence Recording Server SoftwareApplication · Cisco
CVE-2011-0386
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 XML-RPC implementation on Cisco TelePresence Recording Server devices with software 1.6.x and 1.7.x before 1.7.1 allows remote attackers to overwrite files and consequently execute arbitrary code via a malformed request, aka Bug ID CSCti50739.
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 XML-RPC implementation on Cisco TelePresence Recording Server devices versions 1.6.x and 1.7.x before 1.7.1 contains a vulnerability allowing remote attackers to send malformed requests that overwrite arbitrary files on the device, leading to arbitrary code execution. This is a critical network-exploitable flaw in the XML-RPC service.
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
= 1.6.1= 1.6.2= 1.6.3= 1.7.0= 1.7.1
Telepresence Recording ServerHardware / 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 Cisco TelePresence Recording Server deviceLocate the device or software in your environment and confirm it is a Cisco TelePresence Recording Server product. Check the device hostname, management interface, or software inventory for the product name.Affected if The device or software is confirmed as a Cisco TelePresence Recording Server
-
Check the installed software versionAccess the device administrative interface or use the command line interface to retrieve the running software version. Compare this version number against the affected range: 1.6.1, 1.6.2, 1.6.3, 1.7.0, or any version 1.6.x or 1.7.x prior to 1.7.1.Affected if The installed version is 1.6.1, 1.6.2, 1.6.3, 1.7.0, or any 1.6.x or 1.7.x version before 1.7.1
-
Verify the XML-RPC service is accessibleCheck the device network configuration and firewall rules to determine if the XML-RPC service port (typically TCP port 80 or 443 for web-based XML-RPC) is exposed to network accessible interfaces. Use a network scan or review device access control lists.Affected if The XML-RPC service port is reachable from network segments that contain untrusted users or systems
A user is affected if they are running Cisco TelePresence Recording Server version 1.6.1 through 1.7.0 and the XML-RPC service is network-accessible.
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 dataUpgrade Cisco TelePresence Recording Server software to version 1.7.1 or later to patch the malformed request handling in the XML-RPC implementation. If immediate patching is not possible, consider network segmentation to limit exposure of the XML-RPC service to untrusted networks.
Fix this in Telepresence Recording Server Software
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing8.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,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0386 — 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-0386 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