dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2011-0375

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.6.x allows remote authenticated users to execute arbitrary commands via a malformed request, related to "command injection vulnerabilities," aka Bug ID CSCth24671.

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 allows remote authenticated users to execute arbitrary commands via malformed HTTP requests. Affected versions are software 1.2.x through 1.6.x.

MitigationUpgrade Cisco TelePresence endpoint devices to a patched software version beyond 1.6.x, and restrict administrative interface access to trusted authenticated users only.

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= 1.6.0= 1.6.2= 1.6.3
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 TelePresence device model
    Access the device admin interface or use SNMP to query the device hardware model. Common model numbers include CTS-1000, CTS-1100, CTS-3000, CTS-1300, CTS-3200, and CTS-500.
    Affected if The device model is one of: System 1000, System 1100, System 3000, System 1300 Series, System 3200 Series, or System 500 Series (all versions are affected)
  2. Determine the installed software version
    Log into the device CLI or web admin interface and locate the software version information, typically found under 'System Information' or 'Software Version' in the administration menu.
    Affected if The installed software version falls within 1.2.x through 1.6.x range, specifically versions 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, 1.6.0, 1.6.2, or 1.6.3
  3. Verify if the web-based CGI interface is enabled
    Check the device configuration for HTTP or HTTPS web interface settings. This is typically found under 'Network Settings' or 'Administration > Network > HTTP Server' in the device web interface.
    Affected if The HTTP or HTTPS web interface is enabled and accessible from network segments accessible to users
  4. Confirm remote authentication is configured
    Review the device authentication settings to determine if local or remote (RADIUS/TACACS) user accounts are enabled for web interface access.
    Affected if User authentication is enabled for the web interface, allowing remote authenticated users to send HTTP requests

The environment is affected if the device is a Cisco TelePresence System (1000, 1100, 3000, 1300, 3200, or 500) running software version 1.2.x through 1.6.x with the web CGI interface accessible to remote authenticated users.

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

Upgrade Cisco TelePresence endpoint devices to a patched software version beyond 1.6.x, and restrict administrative interface access to trusted authenticated users only.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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