dbcve.org
Telepresence Recording Server SoftwareApplication · Cisco

CVE-2011-0392

HIGH · 7.5 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 →
84/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 do not require authentication for an XML-RPC interface, which allows remote attackers to perform unspecified actions via a session on TCP port 8080, aka Bug ID CSCtg35833.

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 Cisco TelePresence Recording Server devices running software version 1.6.x contain an authentication bypass vulnerability in their XML-RPC interface on TCP port 8080. Remote unauthenticated attackers can exploit this to perform unspecified administrative actions on the recording server, potentially compromising recorded meetings and system configuration.

MitigationApply the vendor patch or upgrade to a fixed Cisco TelePresence software version. Additionally, restrict network access to TCP port 8080 using firewall rules or network segmentation until the patch can be applied.

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

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
Partial
Integrity
Partial
Availability
Partial

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

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 Cisco TelePresence Recording Server
    Check system inventory or documentation for the presence of a Cisco TelePresence Recording Server device. Look for hardware model numbers or confirm via network scanning that the device exists on the network.
    Affected if The target system is confirmed to be a Cisco TelePresence Recording Server.
  2. Check software version
    Access the device admin interface or use SNMP to query the running software version. On the device CLI, use 'show version' or check the web admin panel for the software release number.
    Affected if The installed software version is 1.6.1, 1.6.2, 1.6.3, or any version if the vendor note 'all versions' applies to your deployment.
  3. Verify TCP port 8080 is exposed
    Scan the target device for open TCP port 8080 using nmap (nmap -p 8080 <target_ip>) or netcat (nc -zv <target_ip> 8080). Check firewall rules to determine if the port is accessible from external or untrusted networks.
    Affected if TCP port 8080 is open and reachable from an untrusted network segment.
  4. Test XML-RPC interface accessibility
    Send an HTTP request to the XML-RPC endpoint on port 8080. Use curl: curl -X POST http://<target_ip>:8080/ -d '<?xml version="1.0"?><methodCall><methodName>system.listMethods</methodName></methodCall>'. A valid XML-RPC response indicates the interface is exposed.
    Affected if The XML-RPC interface responds with valid XML-RPC data, confirming the service is accessible without authentication.
  5. Confirm authentication bypass exists
    Attempt to invoke an administrative XML-RPC method without providing credentials. For example, curl -X POST http://<target_ip>:8080/ with a method like 'getRecordings' or 'deleteRecording'. Successful execution without login indicates the vulnerability is present.
    Affected if Administrative XML-RPC methods execute successfully without requiring authentication credentials.

If the system is a Cisco TelePresence Recording Server with TCP port 8080 accessible and the XML-RPC interface allows unauthenticated administrative commands, the environment is affected by CVE-2011-0392.

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

Apply the vendor patch or upgrade to a fixed Cisco TelePresence software version. Additionally, restrict network access to TCP port 8080 using firewall rules or network segmentation until the patch can be applied.

Fix this in Telepresence Recording Server Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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