# CVE-2023-20004: Cisco TelePresence Collaboration Endpoint and RoomOS Software Arbitrary File Write Vulnerability

> Authenticated local attackers can overwrite arbitrary files on Cisco TelePresence devices via symbolic link manipulation in the CLI.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-fvq9-6j72-7gcv

## What is CVE-2023-20004?

CVE-2023-20004 is a medium-severity path traversal vulnerability in Cisco RoomOS Software, published on 15 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Three vulnerabilities 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.

These vulnerabilities are due to improper access controls on files that are on the local file system. An attacker could exploit these vulnerabilities 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 these vulnerabilities, an attacker would need to have a remote support user account.
Note: CVE-2023-20092 does not affect Cisco DX70, DX80, TelePresence MX Series, or TelePresence SX Series devices.
Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2023-20004?

It affects 2 products.


Products: Cisco Roomos, Cisco Telepresence Collaboration Endpoint.

## How do I fix CVE-2023-20004?

No fix has been published for CVE-2023-20004 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-20004 being exploited?

There is no known exploitation of CVE-2023-20004 in the wild and no public exploit code.

## Other vulnerabilities in Cisco RoomOS Software

- [CVE-2026-20150](https://insights.sbomify.com/CVE-2026-20150/): Cisco RoomOS Security Hardening Release - Access Control Vulnerabilities (high 8.8)
- [CVE-2019-15288](https://insights.sbomify.com/CVE-2019-15288/): Cisco TelePresence Collaboration Endpoint, TelePresence Codec, and RoomOS Software Privilege Escalation Vulnerability (high 8.8)
- [CVE-2026-20156](https://insights.sbomify.com/CVE-2026-20156/): Cisco RoomOS Security Hardening Release - Buffer Management Vulnerabilities (high 8.1)
- [CVE-2026-20153](https://insights.sbomify.com/CVE-2026-20153/): Cisco RoomOS Security Hardening Release - Input Validation Vulnerabilities (high 7.5)
- [CVE-2026-20157](https://insights.sbomify.com/CVE-2026-20157/): Cisco RoomOS Security Hardening Release - Missing Encryption Vulnerabilities (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-20004 and fix it if it is affected.

What it is: CVE-2023-20004 is a medium-severity path traversal vulnerability in Cisco RoomOS Software, published on 15 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-20004 in the wild and no public exploit code.

Affected product: Cisco RoomOS Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-20004/ (Markdown: https://insights.sbomify.com/CVE-2023-20004/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-20004
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-20004
- OSV: https://osv.dev/vulnerability/CVE-2023-20004

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-20004/
Summaries are generated and may contain mistakes; the official description above is the record.