CVE-2023-20008
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 · uneditedA vulnerability in the CLI of Cisco TelePresence CE and RoomOS Software could allow an authenticated, local attacker to overwrite arbitrary files on the local system of an affected device. This vulnerability is due to improper access controls on files that are in 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.
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 confidenceA vulnerability in the CLI of Cisco TelePresence CE and RoomOS Software allows an authenticated, local attacker to overwrite arbitrary files on the device. This is due to improper access controls on local filesystem files. An attacker exploits this by placing a symbolic link in a specific location, enabling arbitrary file overwrite.
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= 10.3.2.0= 10.3.4.0= 10.8.2.5= 10.8.4.0= 10.11.3.0= 10.11.5.2= 10.15.3.0= 8.0.0= 8.0.1= 8.1.0= 8.1.1= 8.2.0= 8.2.1= 8.2.2= 8.3.0= 8.3.1= 8.3.2= 8.3.3= 8.3.5= 7.3.5= 7.3.6= 7.3.7= 7.3.9= 7.3.13= 7.3.21CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed RoomOS versionRun 'xcommand SystemUnit Info' or check the version via the web interface under Home > System InformationAffected if The displayed version matches any of these: 10.3.2.0, 10.3.4.0, 10.8.2.5, 10.8.4.0, 10.11.3.0, 10.11.5.2, 10.15.3.0
-
Identify installed TelePresence Collaboration Endpoint versionRun 'xcommand SystemUnit Info' or check the version in the system information pageAffected if The displayed version matches any of these: 8.0.0, 8.0.1, 8.1.0, 8.1.1, 8.2.0, 8.2.1, 8.2.2, 8.3.0, 8.3.1, 8.3.2, 8.3.3, 8.3.5
-
Identify installed TelePresence TC versionRun 'xcommand SystemUnit Info' or check the version in the system information pageAffected if The displayed version matches any of these: 7.3.5, 7.3.6, 7.3.7, 7.3.9, 7.3.13, 7.3.21
-
Verify local CLI authentication is configuredCheck if local user accounts are enabled on the device via 'xcommand Authentication LocalList' or by reviewing CLI access settings in the web interface under Security > Local Users and AuthenticationAffected if Local user accounts or local authentication is enabled and the device is running an affected version
-
Inspect for suspicious symlinks in writable directoriesFrom the CLI, run 'ls -la' on directories that allow file creation, looking for symlinks that may have been placed to redirect file writes to sensitive locationsAffected if Unexpected symlinks exist in locations writable by authenticated CLI users on an affected version
The device is affected if it runs any of the listed versions AND has local CLI authentication enabled, allowing an authenticated attacker to place symlinks for arbitrary file overwrite.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor patch from Cisco's security advisory. Since exploitation requires authenticated local access, enforce strict access controls on device CLI and limit privileged access to trusted administrators only.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20008 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-20008 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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