dbcve.org
ExpresswayApplication · Cisco

CVE-2022-20813

MEDIUM · 5.9 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 · moderate confidence

Multiple vulnerabilities in the API and web-based management interface of Cisco Expressway Series (Expressway-C and Expressway-E) and Cisco TelePresence VCS allow remote attackers to overwrite arbitrary files on the affected device or conduct null byte poisoning attacks. The file overwrite capability could enable code execution or denial of service.

MitigationApply the Cisco security updates for CVE-2022-20813 to the Expressway-C, Expressway-E, or VCS devices. If patches are unavailable, restrict network access to the management interfaces to trusted sources 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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 management interface and check the product name on the login page or system information page, or run 'xCommand SystemUnit Product' via the CLI
    Affected if Product is Cisco Expressway (Expressway-C or Expressway-E) or Cisco TelePresence Video Communication Server
  2. Determine the software version
    In the web UI, go to Status > System or use CLI command 'xCommand SystemUnit Software Version'. Alternatively, check the login page footer which often displays the version
    Affected if Version is below x14.0.7 (for example, x14.0.6, x14.0.5, or earlier)
  3. Verify the management interface is accessible
    Check if the web-based management interface (HTTPS port 443) or API endpoints are reachable from untrusted networks. Use 'show interface' or check firewall rules to confirm exposure
    Affected if Management interface is exposed to internet or untrusted networks
  4. Check for recent authentication logs
    Review system logs under Maintenance > Diagnostics > Log Files for any unauthorized file upload attempts or anomalous API requests, especially POST requests to file upload endpoints

A user is affected if they are running Cisco Expressway or TelePresence VCS with a version below x14.0.7 and the management interface is accessible (even from internal networks, as the vulnerability can be exploited by any authenticated or potentially unauthenticated remote attacker).

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 Cisco security updates for CVE-2022-20813 to the Expressway-C, Expressway-E, or VCS devices. If patches are unavailable, restrict network access to the management interfaces to trusted sources only.

Recommended fix High confidence

x14.0.7

  1. Backup the current Expressway/VCS configuration before starting the upgrade
  2. Download the x14.0.7 software release from Cisco (tools.cisco.com or Cisco Software Download center)
  3. Access the web-based management interface of the affected device
  4. Navigate to the maintenance or upgrade section of the administration interface
  5. Upload the x14.0.7 software image file to the device
  6. Initiate the software upgrade process and allow it to complete
  7. After reboot, verify the device is running version x14.0.7 in the system information page
  8. Confirm that the web interface and API are accessible and functioning normally

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-20813 — 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-20813 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