dbcve.org
Telepresence Collaboration EndpointApplication · Cisco

CVE-2022-20776

MEDIUM · 6.7 CVSS v3.1 Published 2022-10-26
Fix available
A fix is available. Upgrade to 10.20.1 or later.
See remediation →
69/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 · high confidence

Multiple vulnerabilities in Cisco TelePresence Collaboration Endpoint (CE) and RoomOS Software allow path traversal attacks, unauthorized access to sensitive data, and writing arbitrary files to the device's filesystem. These file handling vulnerabilities in the web interface or API components enable attackers to escape intended directory restrictions.

MitigationApply the vendor-supplied firmware/software updates referenced in the Cisco advisory to remediate these vulnerabilities. Restrict network access to management interfaces to trusted sources.

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.20.1
RoomosOperating system
Affected:< 10.20.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Check installed software version
    Access the device admin interface or use the command 'xStatus' via the API to retrieve the current software version. Alternatively, log in to the device and run 'systemunit version' or check the about page in the web interface.
    Affected if The installed version is Cisco TelePresence CE or RoomOS below version 10.20.1
  2. Verify web interface status
    Log into the device command line (SSH or serial) and run the command 'xConfiguration Httpd Mode' to check if the built-in HTTP server is enabled.
    Affected if The HTTP/HTTPS web interface is enabled (mode is ON) on a version below 10.20.1
  3. Check API accessibility
    Run 'xConfiguration Httpd Api Mode' to verify whether the device API (HTTP/HTTPS) is accessible.
    Affected if The API is enabled and accessible on a version below 10.20.1
  4. Review network exposure
    Check the device network configuration using 'xConfiguration Network 1' or review the firewall rules to determine if management ports (80, 443, 22) are reachable from untrusted networks.
    Affected if Management interfaces are exposed to untrusted networks and the software version is below 10.20.1

A user is affected if the device runs Cisco TelePresence CE or RoomOS software version below 10.20.1 and has the web interface or API enabled and 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.

dbcve · scoped
Upgrade available Upgrade to 10.20.1 or later
Fixed in 10.20.1
Interim mitigation

Apply the vendor-supplied firmware/software updates referenced in the Cisco advisory to remediate these vulnerabilities. Restrict network access to management interfaces to trusted sources.

Recommended fix Moderate confidence

Cisco RoomOS/Telepresence CE version 10.20.1

  1. 1. Identify all affected Cisco TelePresence Collaboration Endpoint and RoomOS devices in your inventory
  2. 2. Review the current software version on each device using the web interface or CLI command: 'xStatus systemUnit'
  3. 3. Download Cisco RoomOS software version 10.20.1 or later from the Cisco Software Download Center (requires valid Cisco service contract)
  4. 4. Upload the new software image to each affected device via the web interface (Administration > Software Upgrade) or via CLI using 'file put' command
  5. 5. Initiate the upgrade and allow the device to reboot into the new version
  6. 6. After reboot, verify the new version is installed by running 'xStatus systemUnit' and confirming the software version is 10.20.1 or later
  7. 7. Verify that affected functionality continues to operate normally post-upgrade
Caveat No specific breaking changes documented in the advisory; standard upgrade precautions apply (backup configuration, ensure maintenance window)

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

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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