Telepresence System SoftwareApplication · Cisco
CVE-2011-0372
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 CGI implementation on Cisco TelePresence endpoint devices with software 1.2.x through 1.5.x allows remote attackers to execute arbitrary commands via a malformed request, related to "command injection vulnerabilities," aka Bug ID CSCtb31640.
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 confidenceCommand injection vulnerability in the CGI implementation on Cisco TelePresence endpoint devices running software versions 1.2.x through 1.5.x allows remote attackers to execute arbitrary OS commands via malformed HTTP requests.
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
= 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
all versions
Telepresence System 1100Hardware / appliance
all versions
Telepresence System 3000Hardware / appliance
all versions
Telepresence System 1300 SeriesHardware / appliance
all versions
Telepresence System 3200 SeriesHardware / appliance
all versions
Telepresence System 500 SeriesHardware / 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco TelePresence endpoint deviceAccess the device admin interface or use SNMP/CLI to query the device type. Look for TelePresence System 1000, 1100, 3000, 1300 Series, 3200 Series, or 500 Series in the device inventory or system information.Affected if Device is any of the listed TelePresence system models
-
Check the installed software versionUse the device CLI command 'show version' or access the web interface System Information page to retrieve the software version number.Affected if Version equals 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 for System 1000/1100/3000/1300/3200/500 series any version is considered affected
-
Verify CGI functionality is enabledCheck the device configuration for CGI or web-based management settings. Use 'show running-config' or access the web server configuration via the admin panel to determine if the CGI interface is active.Affected if CGI implementation is enabled and accessible on the device (this is the attack surface for the vulnerability)
User is affected if they have a Cisco TelePresence endpoint device running any of the listed software versions with CGI interface enabled and accessible via HTTP.
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 endpoint devices to a software version beyond 1.5.x that addresses this vulnerability, or apply vendor-provided patches if available.
Fix this in Telepresence System Software
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0372 — 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-0372 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