Telepresence Collaboration EndpointApplication · Cisco

CVE-2022-20955

HIGH · 7.1 CVSS v3.1 Published 2022-10-26
Fix available
A fix is available. Upgrade to 10.19.1 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Multiple vulnerabilities in Cisco TelePresence Collaboration Endpoint (CE) Software and Cisco RoomOS Software could allow an attacker to conduct path traversal attacks, view sensitive data, or write arbitrary files on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.

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 · moderate confidence

Multiple vulnerabilities in Cisco TelePresence Collaboration Endpoint (CE) and RoomOS software allow authenticated attackers to conduct path traversal attacks, view sensitive data, and write arbitrary files to the filesystem of affected devices. These combined capabilities could enable full system compromise.

MitigationApply Cisco software updates when available; prior to patching, restrict network access to collaboration endpoints and disable unnecessary services to reduce attack surface.

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 Collaboration EndpointApplication
Affected:< 10.19.1
RoomosOperating 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 the device product and software
    Access the device admin interface or use CLI command 'xstatus systemunit' to determine if the device is running Cisco TelePresence Collaboration Endpoint (CE) or RoomOS software
    Affected if Device is identified as Cisco TelePresence Collaboration Endpoint or RoomOS
  2. Determine the installed software version
    In the device admin interface, navigate to Settings > System Information, or use CLI command 'systemunit --version' to retrieve the exact software version number
    Affected if Version is below 10.19.1 for Cisco TelePresence Collaboration Endpoint, or any version number for Cisco RoomOS
  3. Verify web-based management is accessible
    Attempt to access the device web interface at its IP address (https://<device-ip>) or check if HTTP/HTTPS services are listening using 'netstat' or similar network utility
    Affected if The device web interface is reachable over the network (this is the attack vector for authenticated path traversal)
  4. Check for unauthorized file access or creation
    Review system logs under /var/log/ or via the device's logging interface for suspicious file operations, unusual path traversal patterns (../../), or unexpected file writes
    Affected if Logs show path traversal attempts or unauthorized file write operations to directories outside expected web application paths

Device is affected if it is Cisco TelePresence Collaboration Endpoint with version lower than 10.19.1, or any version of Cisco RoomOS, and has its web management interface network-accessible.

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
Upgrade available Upgrade to 10.19.1 or later
Fixed in 10.19.1
Interim mitigation

Apply Cisco software updates when available; prior to patching, restrict network access to collaboration endpoints and disable unnecessary services to reduce attack surface.

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20955 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20955 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