dbcve.org
Telepresence Tc SoftwareApplication · Cisco

CVE-2016-1387

CRITICAL · 9.8 CVSS v3.0 Published 2016-05-05
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 XML API in TelePresence Codec (TC) 7.2.0, 7.2.1, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, and 7.3.5 and Collaboration Endpoint (CE) 8.0.0, 8.0.1, and 8.1.0 in Cisco TelePresence Software mishandles authentication, which allows remote attackers to execute control commands or make configuration changes via an API request, aka Bug ID CSCuz26935.

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 XML API in Cisco TelePresence Codec (TC) and Collaboration Endpoint (CE) software mishandles authentication, allowing unauthenticated remote attackers to execute arbitrary control commands or modify system configuration via specially crafted API requests. This is a critical authentication bypass vulnerability in the XML API component.

MitigationUpgrade to a Cisco-supported patched version of the TelePresence software. If immediate patching is not possible, restrict network access to the XML API to trusted management networks 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 Tc SoftwareApplication
Affected:= 7.2.0= 7.2.1= 7.3.0= 7.3.1= 7.3.2= 7.3.3

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Determine the installed TelePresence TC software version
    Access the device admin interface or use CLI command 'xstatus systemunit' or similar to retrieve the current software version
    Affected if The displayed version matches 7.2.0, 7.2.1, 7.3.0, 7.3.1, 7.3.2, or 7.3.3 exactly
  2. Verify XML API service status
    Check the device configuration for XML API enablement via admin web interface under 'APIs' or 'Integration' settings, or use CLI command to query API configuration
    Affected if XML API is enabled on the device
  3. Identify XML API listening port
    Check network listening services on the device (typically port 80/443 for HTTP/HTTPS or a dedicated API port) to confirm XML API is actively listening
    Affected if XML API port is open and listening for connections
  4. Confirm XML API network accessibility
    From an external host, attempt to reach the XML API endpoint (e.g., curl http://<device-ip>/putxml or similar API endpoint) without providing credentials
    Affected if API requests are accepted and processed without authentication being enforced
  5. Test authentication enforcement on XML API
    Send a crafted XML API request to the device without valid credentials and observe whether the command is executed or rejected
    Affected if The device accepts and processes API commands without requiring valid authentication credentials

A user is affected if the device runs TelePresence TC version 7.2.0 through 7.3.3 and has the XML API enabled and accessible, allowing unauthenticated API command execution.

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 to a Cisco-supported patched version of the TelePresence software. If immediate patching is not possible, restrict network access to the XML API to trusted management networks only.

Recommended fix Moderate confidence

Upgrade to TC 7.3.6 or later, or CE 8.1.1 or later (consult Cisco for exact fixed release)

  1. 1. Identify the exact TC or CE software version currently running on the Cisco TelePresence device using the command 'xStatus' or checking via the web interface
  2. 2. Access the Cisco Software Download page at tools.cisco.com or the Cisco Product Security page to obtain the fixed software release
  3. 3. Download the appropriate fixed software version for your device (TC 7.3.6 or later, or CE 8.1.1 or later)
  4. 4. Back up the current device configuration via the web interface (System > Configuration > Backup) or using the API command 'xCommand SystemUnit Backup'
  5. 5. Upload the new software image via the device web interface (System > Software Upgrade) or via FTP/SCP to the device
  6. 6. Reboot the device to apply the new software version
  7. 7. After reboot, verify the new version is installed using 'xStatus' command
  8. 8. Confirm XML API authentication is properly enforced by testing with invalid credentials
Caveat Review Cisco release notes for compatibility with existing infrastructure and any feature changes before upgrading

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

Fix this in Telepresence Tc Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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