CVE-2022-20811
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 · uneditedMultiple vulnerabilities in Cisco TelePresence Collaboration Endpoint (CE) Software and Cisco RoomOS Software could allow an attacker to conduct path traversal attacks, view sensitive data, or write arbitrary files on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.
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 · moderate confidenceMultiple vulnerabilities in Cisco TelePresence Collaboration Endpoint (CE) and RoomOS software allow path traversal attacks, enabling attackers to view sensitive data and write arbitrary files on affected devices. The combination of information disclosure and arbitrary file write capabilities makes this particularly dangerous as it could lead to complete device compromise.
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>= 9.0.0.0, < 9.15.13.0>= 10.0.0.0, < 10.15.2.2< 10.15.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and software versionAccess the device web interface and navigate to the About page, or connect via SSH and run the 'xStatus SystemUnit Software' commandAffected if The installed version falls within >= 9.0.0.0 and < 9.15.13.0, OR >= 10.0.0.0 and < 10.15.2.2 for Cisco TelePresence Collaboration Endpoint, OR < 10.15.1 for Cisco RoomOS
-
Verify web interface is accessibleAttempt to reach the device HTTP/HTTPS web interface from a network locationAffected if The web interface responds and is reachable - this is the primary attack vector for the path traversal vulnerability
-
Confirm API or file transfer services are enabledCheck if the device has HTTP file upload, API endpoints, or FTP/SFTP services enabled via 'xConfiguration' commands or the web interfaceAffected if These services are enabled and exposed, allowing the arbitrary file write portion of the attack to succeed
-
Review recent file access logsExamine system logs via the web interface or 'xFeedback' events for unusual file access patterns, especially attempts to access system directories outside the web rootAffected if Logs show access to paths like '../' or attempts to traverse outside expected directories
The device is affected if it runs an unpatched Cisco TelePresence CE or RoomOS version within the affected ranges AND has its web interface or API services exposed on the network.
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.
dbcve · scoped9.15.13.010.15.110.15.2.2
Apply Cisco's patches for affected software versions; restrict network access to collaboration endpoints and monitor for unauthorized file access or modification attempts.
Telepresence CE: upgrade to 9.15.13.0 or later, or 10.15.2.2 or later; RoomOS: upgrade to 10.15.1 or later
- 1. Determine the current software version by accessing the web interface of the Telepresence device and navigating to Settings > Version, or by using the CLI command 'xversion'
- 2. Identify the product model: for Telepresence Collaboration Endpoint (CE) devices, note whether the current version starts with 9.x or 10.x; for RoomOS devices, note the version number
- 3. If running Telepresence CE version 9.x (9.0.0.0 through 9.15.12.x), download Cisco Telepresence CE version 9.15.13.0 or later from the Cisco Software Download center
- 4. If running Telepresence CE version 10.x (10.0.0.0 through 10.15.2.1), download Cisco Telepresence CE version 10.15.2.2 or later from the Cisco Software Download center
- 5. If running RoomOS (any version below 10.15.1), download Cisco RoomOS version 10.15.1 or later from the Cisco Software Download center
- 6. Upload the firmware file through the device web interface under Maintenance > Software Upgrade, or via CLI using the command 'software upgrade <filename>'
- 7. After upgrade completes, verify the new version by checking Settings > Version or using 'xversion' command
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20811 — 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-2022-20811 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