Telepresence Recording Server SoftwareApplication · Cisco

CVE-2011-0382

HIGH · 10.0 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 →
100/100
Remediation priority · Urgent
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
The CGI subsystem on Cisco TelePresence Recording Server devices with software 1.6.x before 1.6.2 allows remote attackers to execute arbitrary commands via a request to TCP port 443, related to a "command injection vulnerability," aka Bug ID CSCtf97221.

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 CGI subsystem on Cisco TelePresence Recording Server devices running software versions 1.6.x before 1.6.2 contains a command injection vulnerability. Attackers can execute arbitrary OS commands by sending specially crafted requests to the web interface on TCP port 443 (HTTPS), likely through improper sanitization of user input in CGI scripts.

MitigationUpgrade Cisco TelePresence Recording Server software to version 1.6.2 or later to patch the command injection vulnerability. If immediate patching is not possible, restrict network access to the management interface on port 443.

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
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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco TelePresence Recording Server installation
    Locate the device or software running Cisco TelePresence Recording Server. This is typically a dedicated recording server appliance or software instance in a Cisco TelePresence deployment.
    Affected if The system is a Cisco TelePresence Recording Server device or software instance.
  2. Check installed software version
    Access the device management interface or use the command-line interface to retrieve the software version. Common methods include logging into the web UI (HTTPS port 443) or using SNMP to query the system. Look for version information in the about or system status pages.
    Affected if The installed version is 1.6.1, or any 1.6.x version earlier than 1.6.2.
  3. Verify HTTPS web interface is enabled
    Confirm that the web interface on TCP port 443 is accessible and responding. Attempt to reach the device via https://<device-ip>/ or test port 443 connectivity using nc -zv <device-ip> 443 or telnet <device-ip> 443.
    Affected if The HTTPS web interface on port 443 is exposed and responding to requests.
  4. Confirm CGI subsystem is active
    The vulnerability exists in the CGI subsystem. Check if CGI scripts are accessible on the web server. Common indicators include the presence of CGI script endpoints (typically in /cgi-bin/ or with .cgi/.pl extensions) or by reviewing the web server configuration for CGI handler mappings.
    Affected if The CGI subsystem is enabled and processing requests on the web interface.

A system is affected if it is a Cisco TelePresence Recording Server running software version 1.6.1 or any 1.6.x version prior to 1.6.2, with the HTTPS web interface (port 443) and CGI subsystem 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco TelePresence Recording Server software to version 1.6.2 or later to patch the command injection vulnerability. If immediate patching is not possible, restrict network access to the management interface on port 443.

Recommended fix High confidence

Cisco TelePresence Recording Server Software version 1.6.2 or later

  1. 1. Identify the current installed version of Cisco TelePresence Recording Server Software
  2. 2. If version is 1.6.1 or any 1.6.x version before 1.6.2, plan for upgrade
  3. 3. Obtain Cisco TelePresence Recording Server software version 1.6.2 or later from Cisco
  4. 4. Follow Cisco's standard upgrade procedures for TelePresence Recording Server devices
  5. 5. Verify the upgrade was successful and the version is 1.6.2 or later
  6. 6. Test that the CGI subsystem is functioning normally after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Telepresence Recording Server Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-0382 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