dbcve.org
Telepresence Te SoftwareApplication · Cisco

CVE-2014-2170

HIGH · 9.0 CVSS v2.0 Published 2014-05-02
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
Cisco TelePresence TC Software 4.x and 5.x before 5.1.7 and 6.x before 6.0.1 and TE Software 4.x and 6.0 allow remote authenticated users to execute arbitrary commands by using the commands as arguments to tshell (aka tcsh) scripts, aka Bug ID CSCue60202.

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 Cisco TelePresence TC and TE software allows remote authenticated users to execute arbitrary OS commands by passing them as arguments to tshell (tcsh) scripts, bypassing normal command boundaries.

MitigationUpgrade Cisco TelePresence TC Software to version 5.1.7 or later (4.x/5.x) or 6.0.1 or later (6.x); TE Software should be upgraded to patched versions. Apply within the maintenance window after testing in a non-production environment.

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 Te SoftwareApplication
Affected:= 4.1.0= 4.1.1= 4.1.2= 4.1.3= 6.0
Telepresence Tc SoftwareApplication
Affected:= 4.0.0= 4.0.1= 4.0.4= 4.1.1= 4.1.2= 4.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 5.0.0= 5.0.1

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 Cisco TelePresence software type
    Access the device CLI via SSH or console and run 'show version' or 'systeminvoked software' to identify if TC or TE software is installed
    Affected if The device runs Cisco TelePresence TC or TE software
  2. Check installed version against affected list
    Run 'show version' to display the software version number, or query the web interface system information page
    Affected if The version matches any of: TE: 4.1.0, 4.1.1, 4.1.2, 4.1.3, 6.0; TC: 4.0.0, 4.0.1, 4.0.4, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 5.0.0, 5.0.1
  3. Verify remote management interface is accessible
    Confirm the web interface (port 443) or API endpoint is reachable from the network
    Affected if Remote management interfaces are exposed without proper network segmentation
  4. Check for tshell command access
    Attempt to access the tshell endpoint or command interface via the web API, or review configuration for tshell script execution permissions
    Affected if The tshell/tcsh script execution feature is enabled and accessible to authenticated users

You are affected if Cisco TelePresence TC or TE software version matches the affected list AND the tshell interface is accessible to authenticated remote 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.

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

Upgrade Cisco TelePresence TC Software to version 5.1.7 or later (4.x/5.x) or 6.0.1 or later (6.x); TE Software should be upgraded to patched versions. Apply within the maintenance window after testing in a non-production environment.

Recommended fix High confidence

TC Software 5.1.7 or later (5.x), TC Software 6.0.1 or later (6.x), TE Software 6.0.1 or later (6.0)

  1. 1. Identify the exact Cisco TelePresence device model and current software version using the command line interface or device management interface.
  2. 2. Determine the software type (TC or TE) currently installed on the device.
  3. 3. Download the fixed software version from the Cisco Software Download Center (tools.cisco.com) or Cisco.com download pages.
  4. 4. For TC Software: If running 5.x, upgrade to version 5.1.7 or later. If running 6.x, upgrade to version 6.0.1 or later.
  5. 5. For TE Software: If running 4.x or 6.0, upgrade to version 6.0.1 or later.
  6. 6. Upload the new software image to the device via SFTP, FTP, or the device's web interface.
  7. 7. Execute the software upgrade following Cisco standard upgrade procedures.
  8. 8. After upgrade, verify the device is running the fixed version.
Caveat Review Cisco release notes for any configuration or feature changes between versions before upgrading; some legacy features may be deprecated

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

Fix this in Telepresence Te Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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