dbcve.org
Telepresence Collaboration EndpointApplication · Cisco

CVE-2022-20793

MEDIUM · 6.8 CVSS v3.1 Published 2024-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

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 pairing process of Cisco TelePresence CE Software and RoomOS Software for Cisco Touch 10 Devices could allow an unauthenticated, remote attacker to impersonate a legitimate device and pair with an affected device. This vulnerability is due to insufficient identity verification. An attacker could exploit this vulnerability by impersonating a legitimate device and responding to the pairing broadcast from an affected device. A successful exploit could allow the attacker to access the affected device while impersonating a legitimate device.There are no workarounds that address this vulnerability.

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

This vulnerability exists in the device pairing mechanism of Cisco TelePresence CE and RoomOS software for Touch 10 devices. An unauthenticated remote attacker can intercept or respond to pairing broadcast requests and impersonate a legitimate device due to insufficient identity verification during the pairing handshake. Successful exploitation grants the attacker unauthorized access to the affected device while masquerading as a trusted paired device.

MitigationApply the vendor-supplied patch from Cisco when available, as no workarounds exist. Until patched, consider network segmentation to limit exposure of pairing broadcast traffic and monitor for unauthorized device associations.

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:= 9.0.1= 9.1.1= 9.1.2= 9.1.3= 9.1.4= 9.1.5= 9.1.6= 9.2.1= 9.2.2= 9.2.3= 9.2.4= 9.9.3
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
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

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 product and version
    Access the device admin interface or use CLI command 'xstatus systemunit' to retrieve the software version. For Touch 10 devices, check the device type and firmware version in the device settings or via 'xstatus device' command.
    Affected if The device runs Cisco TelePresence Collaboration Endpoint version 9.0.1, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.1, 9.2.2, 9.2.3, 9.2.4, or 9.9.3, OR any version of Cisco RoomOS.
  2. Confirm Touch 10 pairing capability
    Check if Touch 10 control is enabled on the device via admin interface under 'Settings' > 'Peripherals' > 'Touch Panels' or use CLI command 'xconfiguration peripherals pairing' to view pairing status.
    Affected if Touch 10 device pairing is enabled or a Touch 10 controller is registered with the system.
  3. Review paired device list
    Access admin interface under 'Settings' > 'Peripherals' > 'Touch Panels' or use CLI command 'xstatus peripherals' to list all registered and paired Touch 10 devices.
    Affected if Any unknown or unauthorized Touch 10 devices appear in the paired devices list.
  4. Check network exposure of pairing service
    Verify network accessibility of port 4433 or the pairing broadcast interface. Use 'xnetwork' CLI commands to review network configuration and ensure pairing traffic is not exposed to untrusted networks.
    Affected if The device pairing broadcast service is accessible from untrusted network segments.

You are affected if your device runs Cisco TelePresence Collaboration Endpoint (any of the listed versions) or any version of Cisco RoomOS, and Touch 10 pairing is enabled.

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

Apply the vendor-supplied patch from Cisco when available, as no workarounds exist. Until patched, consider network segmentation to limit exposure of pairing broadcast traffic and monitor for unauthorized device associations.

Recommended fix Moderate confidence

Fixed release version from Cisco (specific version to be determined from Cisco's security advisory for this CVE)

  1. 1. Identify the exact device model (Telepresence Collaboration Endpoint or RoomOS device)
  2. 2. Navigate to the Cisco Software Downloads page (software.cisco.com)
  3. 3. Search for the specific device model
  4. 4. Locate the fixed release for CVE-2022-20793 in the release notes or security advisories
  5. 5. Download the fixed software version
  6. 6. Follow Cisco's standard upgrade procedure for the device, typically via the web interface or SSH
Caveat Check Cisco release notes for the fixed version for any compatibility or configuration changes

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

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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