dbcve.org
Telepresence Collaboration EndpointApplication · Cisco

CVE-2023-20090

MEDIUM · 6.7 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 9.15.17.4 / 11.1.2.4 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
A vulnerability in Cisco TelePresence CE and RoomOS could allow an authenticated, local attacker to elevate privileges to root on an affected device. This vulnerability is due to improper access control on certain CLI commands. An attacker could exploit this vulnerability by running a series of crafted commands. A successful exploit could allow the attacker to elevate privileges to root. Cisco has released software updates that address this vulnerability. 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 · high confidence

This is a local privilege escalation vulnerability in Cisco TelePresence CE and RoomOS software. An authenticated attacker with local CLI access can exploit improper access control on certain CLI commands to gain root privileges by running a series of crafted commands. The vulnerability requires the attacker to already have authenticated access to the device's command-line interface.

MitigationApply the Cisco software updates that address this vulnerability. There are no workarounds available, so updating to a patched version is the only remediation path.

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.0.0, < 9.15.17.4
RoomosOperating system
Affected:>= 10.0.1.2, < 11.1.2.4

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. Identify the device product type
    Access the CLI and run 'show systemunit' or check the web interface system information to confirm whether the device is running Cisco TelePresence Collaboration Endpoint or Cisco RoomOS firmware.
    Affected if Device is not a Cisco TelePresence CE or RoomOS product
  2. Check installed software version
    Run the command 'xCommand SystemUnit SoftwareVersion' via CLI or check the version displayed in the web admin interface under System Information or Maintenance.
    Affected if Version cannot be determined or device is not a supported product
  3. Compare version against affected ranges
    Review the installed version number. For TelePresence CE: check if version is >= 9.0.0.0 and < 9.15.17.4. For RoomOS: check if version is >= 10.0.1.2 and < 11.1.2.4.
    Affected if Installed version falls within the affected version ranges (9.0.0.0 to 9.15.17.4 for TelePresence CE, or 10.0.1.2 to 11.1.2.4 for RoomOS)
  4. Verify CLI access is configured
    Check if the device has CLI access enabled by reviewing the device's service configuration or admin settings. This can be done via 'show service' or checking the SSH/Telnet service status in the web interface under Security or Services.
    Affected if CLI access (SSH or local console) is enabled on the device - this is required for exploitation

The device is affected if it is a Cisco TelePresence Collaboration Endpoint or RoomOS device running a version within the affected ranges AND has CLI access enabled, allowing an authenticated attacker to potentially escalate privileges to root.

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.17.4 / 11.1.2.4 or later
Fixed in 9.15.17.411.1.2.4
Interim mitigation

Apply the Cisco software updates that address this vulnerability. There are no workarounds available, so updating to a patched version is the only remediation path.

Recommended fix High confidence

Telepresence CE: upgrade to 9.15.17.4 or later | RoomOS: upgrade to 11.1.2.4 or later

  1. 1. Identify the specific product line in use: Telepresence Collaboration Endpoint or RoomOS
  2. 2. For Telepresence Collaboration Endpoint: Upgrade to version 9.15.17.4 or later
  3. 3. For RoomOS: Upgrade to version 11.1.2.4 or later
  4. 4. Access the device admin interface or use the CLI to perform the software update
  5. 5. Verify the upgrade completed successfully and the device is functioning normally
  6. 6. Confirm the new version is running by checking the system information
Caveat Standard upgrade risks apply - review release notes for any configuration or feature changes before upgrading

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

Fix this in Telepresence Collaboration Endpoint Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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