dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 27 Feb 2026.
Catalyst Sd Wan ManagerApplication · Cisco

CVE-2022-20775

HIGH · 7.8 CVSS v3.1 Published 2022-09-30
Fix available
A fix is available. Upgrade to 20.6.3 / 20.7.2 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Public exploit 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
A vulnerability in the CLI of Cisco SD-WAN Software could allow an authenticated, local attacker to gain elevated privileges. This vulnerability is due to improper access controls on commands within the application CLI. An attacker could exploit this vulnerability by running a maliciously crafted command on the application CLI. A successful exploit could allow the attacker to execute arbitrary commands as the root user. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sd-wan-priv-E6e8tEdF

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

This is a local privilege escalation vulnerability in Cisco SD-WAN Software's CLI where improper access controls allow an authenticated attacker to run maliciously crafted commands that execute arbitrary code with root privileges.

MitigationApply the Cisco software update that addresses this vulnerability; there are no available workarounds.

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
Catalyst Sd Wan ManagerApplication
Affected:< 20.6.3>= 20.7, < 20.7.2= 20.8
Sd Wan Vbond OrchestratorApplication
Affected:< 20.6.3>= 20.7, < 20.7.2= 20.8
Sd Wan Vedge CloudWeb browser
Affected:< 20.6.3>= 20.7, < 20.7.2= 20.8
Sd Wan Vsmart ControllerApplication
Affected:< 20.6.3>= 20.7, < 20.7.2= 20.8
Sd WanApplication
Affected:< 20.6.3>= 20.7, < 20.7.2= 20.8

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

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

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

  1. Identify the Cisco SD-WAN product component
    Log into the device CLI and determine the product type (vmanage, vbond, vedge, or vsmart) using commands such as 'show version' or by reviewing the system documentation
    Affected if The device is running any of the affected SD-WAN components (Cisco Catalyst SD-WAN Manager, Vbond Orchestrator, Vedge Cloud, Vsmart Controller, or SD-WAN)
  2. Retrieve the installed software version
    Execute the command to display the running software version, such as 'show version' or 'show system information' from the CLI prompt
    Affected if The version output is displayed and can be compared against the affected ranges
  3. Compare the installed version against affected ranges
    Check if the version falls into any of these vulnerable ranges: versions earlier than 20.6.3, versions 20.7.0 through 20.7.1, or version 20.8
    Affected if The installed version is < 20.6.3 OR (>= 20.7 AND < 20.7.2) OR = 20.8
  4. Confirm CLI access is available
    Verify that CLI access is enabled and accessible on the device (the vulnerability requires authenticated local CLI access to exploit)
    Affected if CLI access is available to an authenticated user on the affected device

The environment is affected if the Cisco SD-WAN device is running any of the listed product components with a version number that falls within < 20.6.3, >= 20.7 but < 20.7.2, or exactly 20.8.

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
Upgrade available Upgrade to 20.6.3 / 20.7.2 or later
Fixed in 20.6.320.7.2
Interim mitigation

Apply the Cisco software update that addresses this vulnerability; there are no available workarounds.

Recommended fix High confidence

Upgrade to Cisco SD-WAN version 20.6.3, or 20.7.2 or later (excluding 20.8)

  1. 1. Identify the current installed version of Cisco SD-WAN software (Manager, Vbond Orchestrator, Vedge Cloud, or Vsmart Controller) using the 'show version' command in the CLI
  2. 2. Based on the current version, plan the upgrade path: if < 20.6.3, upgrade to 20.6.3 or later; if 20.7.x, upgrade to 20.7.2 or later; if 20.8, upgrade to a version higher than 20.8
  3. 3. Download the appropriate fixed software release from Cisco (20.6.3, 20.7.2, or later) from the Cisco software download center
  4. 4. Follow Cisco's standard SD-WAN software upgrade procedure: backup the current configuration, upload the new software image, and execute the upgrade command
  5. 5. After upgrade, verify the new version is running using 'show version' and confirm the vulnerability is resolved
  6. 6. Validate that the system is functioning normally post-upgrade
Caveat Review Cisco SD-WAN release notes for any configuration or compatibility changes between your current version and the target version before upgrading

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

Fix this in Catalyst Sd Wan Manager Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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