dbcve.org
ExpresswayApplication · Cisco

CVE-2022-20812

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-06
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 in the web-based management interface of Cisco Expressway Series and Cisco TelePresence Video Communication Server (VCS) could allow a remote attacker to overwrite arbitrary files or conduct null byte poisoning attacks on an affected device. Note: Cisco Expressway Series refers to the Expressway Control (Expressway-C) device and the Expressway Edge (Expressway-E) 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 · high confidence

Multiple vulnerabilities in the API and web-based management interface of Cisco Expressway Series (Expressway-C and Expressway-E) and TelePresence VCS allow remote attackers to overwrite arbitrary files or conduct null byte poisoning attacks on affected devices.

MitigationApply Cisco-provided patches or firmware updates for Expressway Series and TelePresence VCS. Restrict access to management interfaces to trusted networks only.

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
ExpresswayApplication
Affected:< x14.0.7
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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the product and model
    Access the web-based management interface and locate the System Information page, or use CLI command 'xCommand SystemUnit Info' to determine if the device is Cisco Expressway Series or TelePresence VCS
    Affected if Device is Cisco Expressway (any variant) or TelePresence VCS
  2. Determine the installed firmware version
    In the web interface, go to Status > System information and note the software version displayed, or run 'show version' via CLI
    Affected if Version is lower than 14.0.7 (for example, 14.0.6, 14.0.5, 13.x, etc.)
  3. Verify the web-based management interface is accessible
    Confirm the API and web management interface (typically ports 80/443 or 4433) are reachable from network locations
    Affected if Management interface is exposed to untrusted networks or the internet
  4. Check for unauthorized file modifications
    Review system logs (Maintenance > Diagnostics > Log Downloads) for any unexpected file write operations or unusual API activity related to file upload/overwrite functions
    Affected if Logs show unexpected file overwrite events or suspicious API calls to file handling endpoints

The environment is affected if the device runs Cisco Expressway or TelePresence VCS with firmware version below 14.0.7 and has its web management interface accessible to potential attackers.

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 Cisco-provided patches or firmware updates for Expressway Series and TelePresence VCS. Restrict access to management interfaces to trusted networks only.

Recommended fix High confidence

x14.0.7 or later

  1. 1. Identify the current installed version of Cisco Expressway Series or TelePresence VCS by accessing the web management interface or using the CLI command 'xstatus version'
  2. 2. Navigate to the Cisco Software Download page and download version x14.0.7 or later for your specific appliance model
  3. 3. Back up the current configuration using the web interface (Maintenance > Backup and Restore) or CLI command 'export configuration'
  4. 4. Access the web management interface and go to Maintenance > Software Upgrade
  5. 5. Upload the downloaded software image and initiate the upgrade process
  6. 6. Wait for the upgrade to complete and the system to reboot
  7. 7. Verify the new version by checking System > Information in the web interface or running 'xstatus version' via CLI
  8. 8. Restore the configuration if needed using the backup created in step 3

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

Fix this in Expressway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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