dbcve.org
Telepresence Video Communication ServerApplication · Cisco

CVE-2022-20809

MEDIUM · 6.5 CVSS v3.1 Published 2022-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Multiple vulnerabilities in the API and web-based management interfaces of Cisco Expressway Series and Cisco TelePresence Video Communication Server (VCS) could allow an authenticated, remote attacker to write files or disclose sensitive information 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 confidence

Multiple vulnerabilities in the API and web-based management interfaces of Cisco Expressway Series and Cisco TelePresence VCS allow an authenticated, remote attacker to write arbitrary files or disclose sensitive information on affected devices.

MitigationApply the relevant Cisco firmware updates for Expressway Series and TelePresence VCS. Restrict access to management interfaces to trusted networks and ensure strong authentication controls are in place.

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 Video Communication ServerApplication
Affected:<= x14.0.7

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 installed product
    Access the web-based management interface or check the system information via CLI command 'xstatus systemunit' or 'system-info' to confirm whether the device is Cisco Expressway Series or Cisco TelePresence VCS
    Affected if The device is either Cisco Expressway Series or Cisco TelePresence VCS
  2. Check the firmware version
    In the web interface, go to Maintenance > System or use CLI command 'version' to retrieve the installed firmware version. Compare it against the affected range: version x14.0.7 or earlier for TelePresence VCS
    Affected if The installed version is x14.0.7 or earlier (or any x14.x version <= 14.0.7)
  3. Determine if web-based management is enabled
    Check the web interface status at https://<device-ip>/putmanagementservice or verify via CLI using 'httpd' or 'webengine' status commands. Also check if HTTP/HTTPS management ports (80/443 or 4433) are listening
    Affected if The web-based management interface is enabled and accessible
  4. Verify if API access is available
    Check if the REST API is enabled by accessing https://<device-ip>/putapi or by reviewing the API settings in the web interface under Application > API settings
    Affected if The API interface is enabled and accessible

A user is affected if the device is Cisco TelePresence VCS (or Expressway Series) running firmware version x14.0.7 or earlier with web-based management or API interfaces enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco firmware updates for Expressway Series and TelePresence VCS. Restrict access to management interfaces to trusted networks and ensure strong authentication controls are in place.

Recommended fix Moderate confidence

x14.0.8 or later

  1. 1. Identify the current installed version of Cisco TelePresence Video Communication Server (VCS) via the web UI (System > System overview) or CLI (xCommand SystemUnitVersion).
  2. 2. Download the fixed software version from Cisco (x14.0.8 or later) from the Cisco Software Download center at cisco.com, requiring valid service contract.
  3. 3. Back up the current VCS configuration via the web UI (Maintenance > Backup and restore) or CLI (xCommand Backup).
  4. 4. Upload the new software image via the web UI (Maintenance > Upgrade) or CLI (xCommand SystemUnitSoftwareUpgrade).
  5. 5. Follow the on-screen upgrade progress; the system will reboot automatically upon completion.
  6. 6. After reboot, verify the new version is installed and confirm all services are operational.
  7. 7. Review system logs (Maintenance > Logs) to confirm the upgrade completed without errors.
Caveat Review Cisco release notes for version x14.0.8 for any changes to API behavior, CLI commands, or management interface functionality that may affect existing integrations.

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

Fix this in Telepresence Video Communication Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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