dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2011-0373

HIGH · 9.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 →
96/100
Remediation priority · Urgent
Remotely reachable 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 implementation on Cisco TelePresence endpoint devices with software 1.2.x through 1.5.x allows remote authenticated users to execute arbitrary commands via a malformed request, related to "command injection vulnerabilities," aka Bug ID CSCtb31685.

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

Command injection vulnerability in the CGI implementation on Cisco TelePresence endpoint devices running software versions 1.2.x through 1.5.x allows remote authenticated users to execute arbitrary operating system commands via malformed HTTP requests.

MitigationApply the vendor-supplied patch/firmware update from Cisco for affected TelePresence software versions. If patching is not immediately possible, restrict network access to the CGI interface and limit authenticated user privileges to minimum necessary.

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 System SoftwareApplication
Affected:= 1.2.3= 1.3.2= 1.4.7= 1.5.1= 1.5.3= 1.5.10= 1.5.11= 1.5.12= 1.5.13
Telepresence System 1000Hardware / appliance
Affected:all versions
Telepresence System 1100Hardware / appliance
Affected:all versions
Telepresence System 3000Hardware / appliance
Affected:all versions
Telepresence System 1300 SeriesHardware / appliance
Affected:all versions
Telepresence System 3200 SeriesHardware / appliance
Affected:all versions
Telepresence System 500 SeriesHardware / 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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/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 the device model and software version
    Access the Cisco TelePresence device admin interface or CLI and retrieve the installed software version information. This is typically found in the system information or version section of the web interface, or via the 'show version' command in the CLI.
    Affected if The installed version is 1.2.3, 1.3.2, 1.4.7, 1.5.1, 1.5.3, 1.5.10, 1.5.11, 1.5.12, or 1.5.13, OR the device is a Cisco TelePresence System 1000, 1100, 3000, 1300 Series, 3200 Series, or 500 Series (all versions are affected).
  2. Confirm the CGI web interface is enabled
    Check the device configuration settings for remote web management or CGI interface availability. This is typically found in the web server or administration settings of the TelePresence device.
    Affected if The CGI interface or remote web management is enabled and accessible (the vulnerability exists within the CGI implementation).
  3. Verify if remote authentication is configured
    Review the device authentication settings to determine whether remote authenticated users can access the web interface. Check for local user accounts or integration with external authentication servers (RADIUS, TACACS+).
    Affected if Remote authentication is enabled and allows authenticated users to access the web interface (the command injection requires an authenticated session).
  4. Assess network exposure of the management interface
    Determine if the TelePresence device web interface (CGI) is reachable from outside the trusted internal network. Check firewall rules, NAT configurations, or ACLs applied to the device management interface.
    Affected if The CGI interface is reachable from untrusted networks or the internet, increasing exposure to remote attackers.

A user is affected if their Cisco TelePresence device runs software version 1.2.x through 1.5.x (or is a System 1000/1100/3000/1300/3200/500 of any version), has the CGI interface enabled, and permits remote authenticated access, particularly if exposed to untrusted networks.

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

Apply the vendor-supplied patch/firmware update from Cisco for affected TelePresence software versions. If patching is not immediately possible, restrict network access to the CGI interface and limit authenticated user privileges to minimum necessary.

Recommended fix Moderate confidence

Upgrade to Cisco TelePresence System Software version 1.6.0 or later (beyond the 1.2.x-1.5.x affected range)

  1. Identify the current Cisco TelePresence System Software version running on the device using the CLI command 'show version' or through the web interface
  2. Determine if the current version falls within the affected range (1.2.x through 1.5.x)
  3. Contact Cisco Technical Support or visit the Cisco TelePresence downloads page to obtain the appropriate fixed software release
  4. Obtain the upgrade package for your specific TelePresence System model (1000, 1100, 3000, 1300 Series, 3200 Series, or 500 Series)
  5. Upload the new software image to the device using the CLI command 'software upgrade' or through the web-based administration interface
  6. Reboot the device to apply the new software version
  7. Verify the upgrade was successful by running 'show version' and confirming the new software version is running
Caveat Review Cisco release notes for the target version to check for any configuration or feature changes that may require adjustment

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

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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