CVE-2022-20850
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 stand-alone Cisco IOS XE SD-WAN Software and Cisco SD-WAN Software could allow an authenticated, local attacker to delete arbitrary files from the file system of an affected device. This vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by injecting arbitrary file path information when using commands in the CLI of an affected device. A successful exploit could allow the attacker to delete arbitrary files from the file system of the affected device.
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 vulnerability in the CLI of Cisco IOS XE SD-WAN and Cisco SD-WAN Software allows authenticated local attackers to delete arbitrary files due to insufficient input validation. Attackers can inject malicious file path information into CLI commands to bypass restrictions and remove any file on the affected device's filesystem.
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< 18.4.5< 18.4.5< 18.4.5< 16.10.1< 18.4.5CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco SD-WAN productLog into the device CLI and run 'show version' or 'show sdwan version' to determine which SD-WAN component is running (Vbond Orchestrator, Vmanage, Vsmart Controller, or IOS XE SD-WAN)Affected if The device is running any of the listed SD-WAN products (Vbond, Vmanage, Vsmart, or IOS XE SD-WAN)
-
Check the installed software versionRun 'show version' or 'show sdwan version' and locate the software version number. Compare it to the affected ranges: versions < 18.4.5 for Vbond/Vmanage/Vsmart, or versions < 16.10.1 for IOS XE SD-WANAffected if The installed version is below 18.4.5 (for Vbond/Vmanage/Vsmart) or below 16.10.1 (for IOS XE SD-WAN)
-
Verify CLI access existsConfirm the device has CLI interface available. This vulnerability requires authenticated local CLI access to exploit. Check if CLI accounts exist with 'show users' or similar commandAffected if CLI access is available to any user account on the device
-
Review system logs for file deletion eventsCheck system logs (via 'show log' or logging buffer) for commands that include unusual file path patterns, particularly attempts to delete files outside normal operation directoriesAffected if Logs show CLI commands with suspicious path traversal patterns or unexpected file deletions
The environment is affected if the device runs a vulnerable Cisco SD-WAN product version (below 18.4.5 or below 16.10.1 depending on product) and has CLI access available to authenticated users.
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 · scoped16.10.118.4.5
Apply the vendor-provided patch or upgrade to a fixed software version. Additionally, limit CLI access to trusted personnel only and monitor for unusual or malformed CLI command patterns.
18.4.5 for Vbond Orchestrator, Vmanage, Vsmart Controller, and SD-WAN; 16.10.1 for IOS XE SD-WAN
- Identify the current version of the affected SD-WAN component (Vbond Orchestrator, Vmanage, Vsmart Controller, or IOS XE SD-WAN) using the CLI or management interface
- Download the fixed software version from Cisco (18.4.5 for Vbond/Vmanage/Vsmart/SD-WAN, or 16.10.1 for IOS XE SD-WAN)
- Follow Cisco SD-WAN upgrade procedures to install the fixed software version
- Verify the upgrade was successful by checking the software version post-upgrade
- Ensure only authorized administrative users have CLI access to prevent local authenticated exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20850 — 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-20850 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