dbcve.org
Telepresence Collaboration EndpointApplication · Cisco

CVE-2022-20783

HIGH · 7.5 CVSS v3.1 Published 2022-04-21
Fix available
A fix is available. Upgrade to 9.15.10.8 / 10.11.2.2 or later.
See remediation →
84/100
Remediation priority · High
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
A vulnerability in the packet processing functionality of Cisco TelePresence Collaboration Endpoint (CE) Software and Cisco RoomOS Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending crafted H.323 traffic to an affected device. A successful exploit could allow the attacker to cause the affected device to either reboot normally or reboot into maintenance mode, which could result in a DoS condition on the device.

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 vulnerability in the packet processing functionality of Cisco TelePresence Collaboration Endpoint (CE) Software and Cisco RoomOS Software allows an unauthenticated, remote attacker to cause denial of service by sending crafted H.323 traffic to an affected device. The vulnerability stems from insufficient input validation in the H.323 packet processing path, which can trigger a reboot into either normal or maintenance mode.

MitigationApply Cisco security updates when available. If patches cannot be applied immediately, consider blocking H.323 traffic at the network perimeter or disabling H.323 functionality on affected devices if not required for business operations.

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.15.10.8>= 10.0.0.0, < 10.11.2.2
RoomosOperating system
Affected:< 2022

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 software version
    Access the device admin interface or use CLI to display the software version. For TelePresence CE, check under the web interface Overview page or use command 'xstatus systemunit'. For RoomOS, check under device settings or use equivalent CLI commands.
    Affected if The installed version is Cisco TelePresence CE < 9.15.10.8, or >= 10.0.0.0 but < 10.11.2.2, or any Cisco RoomOS version released prior to 2022
  2. Determine if H.323 protocol is enabled
    Access the device configuration settings. In the web interface, navigate to Setup > Protocols > H.323 or use CLI command 'xConfiguration H323 Mode' to check if H.323 is enabled.
    Affected if H.323 protocol is enabled on the device
  3. Verify network accessibility to H.323 ports
    Review firewall rules and network configuration to determine if the device is reachable on H.323 ports (typically TCP/1720 and UDP ports in the 5555-5560 range) from untrusted networks.
    Affected if The device can receive H.323 traffic from unauthenticated remote sources over the network

The device is affected if it runs a vulnerable Cisco TelePresence CE or RoomOS version AND has H.323 protocol enabled and accessible from the network.

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 9.15.10.8 / 10.11.2.2 / 2022 or later
Fixed in 9.15.10.810.11.2.22022
Interim mitigation

Apply Cisco security updates when available. If patches cannot be applied immediately, consider blocking H.323 traffic at the network perimeter or disabling H.323 functionality on affected devices if not required for business operations.

Recommended fix High confidence

TelePresence CE: 9.15.10.8 or later, or 10.11.2.2 or later | RoomOS: 2022 or later

  1. Check the current software version on the device via the web interface or API (GET /status/device information or through the administration menu)
  2. Identify the product line (Cisco TelePresence Collaboration Endpoint/CE or Cisco RoomOS)
  3. For TelePresence Collaboration Endpoint: If running version 9.x, upgrade to version 9.15.10.8 or later
  4. For TelePresence Collaboration Endpoint: If running version 10.x, upgrade to version 10.11.2.2 or later
  5. For RoomOS: Upgrade to a 2022 release or later (e.g., RoomOS 2022.x)
  6. Download the appropriate software from Cisco's software download center (requires valid Cisco service contract)
  7. Upload the new software bundle to the device via the web interface (Administration > Software Upgrade) or API
  8. Initiate the upgrade and allow the device to reboot into the new version

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

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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