CVE-2022-20930
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 · uneditedA vulnerability in the CLI of Cisco SD-WAN Software could allow an authenticated, local attacker to overwrite and possibly corrupt files on an affected system. This vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by injecting arbitrary commands that are executed as the root user account. A successful exploit could allow the attacker to overwrite arbitrary system files, which could result in a denial of service (DoS) condition.
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 confidenceA command injection vulnerability in the CLI of Cisco SD-WAN Software allows an authenticated local attacker to inject arbitrary commands that execute as root user due to insufficient input validation, enabling arbitrary file overwrite and potential denial of service.
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= 20.8= 20.9< 20.6.2= 20.8= 20.9< 20.6.2< 20.6.2= 20.8= 20.9< 20.6.2= 20.8= 20.9CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 the Cisco SD-WAN product in useLog into the device or check system documentation to determine which SD-WAN component is deployed (vManage, vBond, vSmart, or Catalyst SD-WAN Manager)Affected if The product is any of Cisco SD-WAN vManage, vBond, vSmart, or Catalyst SD-WAN Manager
-
Determine the installed software versionUse the CLI command 'show version' or access the web UI dashboard to retrieve the currently running software version numberAffected if The installed version matches any of these: 20.8, 20.9, or any version earlier than 20.6.2 (for the applicable product)
-
Confirm CLI access is availableVerify that CLI access is enabled and accessible, typically via SSH to the device or console connectionAffected if CLI access exists and the attacker can authenticate as a local user
-
Check for local authenticated user accessReview the list of locally configured users on the device using 'show users' or user management commands in the CLIAffected if Local user accounts exist on the system, providing an authenticated attack vector
-
Identify the vulnerable command interfaceExamine which CLI operational or configuration commands accept user-supplied input that could be leveraged for injectionAffected if The device runs an affected version and accepts unauthenticated or weakly secured CLI input
The environment is likely affected if any Cisco SD-WAN component is running version 20.8, 20.9, or any version prior to 20.6.2, and local CLI authentication is accessible.
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 · scoped20.6.2
Apply Cisco's available patches for CVE-2022-20930; restrict CLI access to trusted local users only until the patch is applied.
Upgrade to 20.6.2 or later; for vManage/vBond/vSmart, 20.6.2 contains the fix. For 20.8/20.9 users, obtain subsequent security update from Cisco.
- 1. Identify the specific Cisco SD-WAN product in use (vManage, vBond, vSmart, or SD-WAN Manager)
- 2. Determine the currently installed version via CLI using 'show version' or the administration interface
- 3. For versions < 20.6.2: Plan upgrade to 20.6.2 or later stable release
- 4. For versions 20.8 or 20.9: Check Cisco release notes for subsequent security updates addressing this vulnerability
- 5. Schedule maintenance window as upgrade will require system restart
- 6. Back up current configuration before proceeding with upgrade
- 7. Obtain upgrade software from Cisco directly via official channels or Cisco Software Central
- 8. Follow Cisco SD-WAN upgrade procedure documented in the migration guide for your specific product
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20930 — 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-20930 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