dbcve.org
Telepresence Collaboration EndpointApplication · Cisco

CVE-2023-20091

MEDIUM · 5.1 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 9.15.17.4 / 11.1.3.1 or later.
See remediation →
53/100
Remediation priority · Moderate
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 CLI of Cisco TelePresence CE and RoomOS could allow an authenticated, local attacker to overwrite arbitrary files on the local file system of an affected device. This vulnerability is due to improper access controls on files that are on the local file system. An attacker could exploit this vulnerability by placing a symbolic link in a specific location on the local file system of an affected device. A successful exploit could allow the attacker to overwrite arbitrary files on the affected device. To exploit this vulnerability, an attacker would need to have a remote support user account. 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

A vulnerability in Cisco TelePresence CE and RoomOS CLI allows an authenticated attacker with a remote support user account to overwrite arbitrary files on the local file system by placing a symbolic link in a specific location, due to improper access controls on local files.

MitigationApply the Cisco software updates that address this vulnerability; no workarounds are available.

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

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

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 installed version
    Access the CLI and run the command to display system information (typically 'xcommand systemunit info' or 'show version'), or check the web admin interface under System Information
    Affected if The version falls within the affected ranges: TelePresence CE >= 9.0.0.0 and < 9.15.17.4, or RoomOS >= 10.0.1.2 and < 11.1.3.1
  2. Confirm the product is TelePresence CE or RoomOS
    Verify the product name from the system information output or web admin interface
    Affected if The product is Cisco TelePresence Collaboration Endpoint or Cisco RoomOS
  3. Check for remote support user accounts
    List user accounts in the system via CLI (typically 'xcommand userlist' or 'show account') or check the user configuration in the web admin interface under Users or Security settings
    Affected if A remote support user account is configured and enabled on the system
  4. Verify CLI access is available
    Confirm that command-line interface access is enabled and accessible via SSH, serial, or console
    Affected if CLI access is available to authenticate with the remote support account credentials

Your environment is affected if you are running a vulnerable version of Cisco TelePresence CE or RoomOS (within the specified version ranges) AND have a remote support user account configured with CLI access.

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.3.1 or later
Fixed in 9.15.17.411.1.3.1
Interim mitigation

Apply the Cisco software updates that address this vulnerability; no workarounds are available.

Recommended fix High confidence

TelePresence CE: 9.15.17.4 or later; RoomOS: 11.1.3.1 or later

  1. 1. Identify the exact product model (TelePresence Collaboration Endpoint or RoomOS device)
  2. 2. Access the device's admin interface or CLI with administrator credentials
  3. 3. Download the appropriate fixed software version from Cisco (9.15.17.4 or later for TelePresence CE, 11.1.3.1 or later for RoomOS)
  4. 4. Upload the software update to the device via the admin web interface or SCP/SFTP
  5. 5. Initiate the software upgrade through the device's upgrade function
  6. 6. Verify the device reboots successfully and confirm the installed version matches the fixed release
  7. 7. Validate that the remote support user account privileges are appropriately configured post-upgrade
Caveat Review Cisco release notes for breaking changes between major versions; some configuration migration may be required

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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