dbcve.org
Ex60 FirmwareOperating system · Cisco

CVE-2020-3143

HIGH · 7.2 CVSS v3.1 Published 2020-09-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
A vulnerability in the video endpoint API (xAPI) of Cisco TelePresence Collaboration Endpoint (CE) Software, Cisco TelePresence Codec (TC) Software, and Cisco RoomOS Software could allow an authenticated, remote attacker to conduct directory traversal attacks on an affected device. The vulnerability is due to insufficient validation of user-supplied input to the xAPI of the affected software. An attacker could exploit this vulnerability by sending a crafted request to the xAPI. A successful exploit could allow the attacker to read and write arbitrary files in the system. To exploit this vulnerability, an attacker would need either an In-Room Control or administrator account.

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

A directory traversal vulnerability in the xAPI (extensible API) of Cisco TelePresence video endpoints (CE, TC, and RoomOS software) allows authenticated attackers (with In-Room Control or administrator accounts) to read and write arbitrary files by crafting malicious requests with path traversal sequences (e.g., ../../). The vulnerability stems from insufficient input validation on user-supplied paths in the xAPI endpoint.

MitigationApply vendor-supplied patches/updates from Cisco for affected CE, TC, and RoomOS software versions. If patches are unavailable, restrict network access to xAPI and disable unused In-Room Control accounts.

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
Ex60 FirmwareOperating system
Affected:all versions
Ex90 FirmwareOperating system
Affected:all versions
Sx10 FirmwareOperating system
Affected:all versions
Sx20 FirmwareOperating system
Affected:all versions
Sx80 FirmwareOperating system
Affected:all versions
Telepresence Codec C40 FirmwareOperating system
Affected:all versions
Telepresence Codec C60 FirmwareOperating system
Affected:all versions
Telepresence Codec C90 FirmwareOperating system
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
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify device model and firmware type
    Access the device web interface or use xCommand SystemUnit to retrieve the product name (e.g., Ex60, Ex90, Sx10, Sx20, Sx80, Codec C40/C60/C90) and firmware type (CE, TC, or RoomOS)
    Affected if The device is one of the listed models: Cisco Ex60, Ex90, Sx10, Sx20, Sx80, or Codec C40/C60/C90
  2. Confirm xAPI endpoint is accessible
    Attempt to reach the xAPI endpoint via HTTP/HTTPS (typically port 443 or 8080) or use the xAPI command-line interface over SSH to send an HTTP request to the device
    Affected if The xAPI endpoint responds to requests - the vulnerability exists in the xAPI service
  3. Check for In-Room Control accounts
    Query the device user database via xAPI using 'xCommand UserManagement List' or check the local user configuration in the web interface under Users or Security settings
    Affected if In-Room Control user accounts are configured on the device
  4. Verify administrator accounts exist
    Query the device for administrator accounts using 'xCommand UserManagement List' or check the Administration settings in the web interface
    Affected if Administrator accounts are present on the device (the vulnerability can be exploited by either In-Room Control or admin accounts)
  5. Assess network exposure of xAPI
    Review firewall rules, ACLs, or network segmentation to determine if the xAPI port (443, 8080, or SSH) is accessible from untrusted networks
    Affected if xAPI is accessible from outside the trusted management network

Your environment is affected if you have any of the listed Cisco TelePresence devices (Ex60, Ex90, Sx10, Sx20, Sx80, Codec C40/C60/C90) with xAPI accessible and at least one In-Room Control or administrator account configured.

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

Apply vendor-supplied patches/updates from Cisco for affected CE, TC, and RoomOS software versions. If patches are unavailable, restrict network access to xAPI and disable unused In-Room Control accounts.

Fix this in Ex60 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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