CVE-2023-20035
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 IOS XE SD-WAN Software could allow an authenticated, local attacker to execute arbitrary commands with elevated privileges. This vulnerability is due to insufficient input validation by the system CLI. An attacker with privileges to run commands could exploit this vulnerability by first authenticating to an affected device using either local terminal access or a management shell interface and then submitting crafted input to the system CLI. A successful exploit could allow the attacker to execute commands on the underlying operating system with root-level privileges. An attacker with limited user privileges could use this vulnerability to gain complete control over the system. Note: For additional information about specific impacts, 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 confidenceCommand injection vulnerability in Cisco IOS XE SD-WAN Software CLI where authenticated attackers can submit crafted input that bypasses insufficient input validation, allowing arbitrary OS command execution with root-level privileges.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the device runs Cisco IOS XE with SD-WANExecute 'show version' and look for 'IOS XE' in the software banner, then run 'show sdwan version' or 'show sdwan control connections' to confirm SD-WAN feature is presentAffected if The device shows both IOS XE and SD-WAN capabilities in the command output
-
Confirm CLI access is availableAttempt to access the CLI via console, SSH, or management interface and verify you can enter privileged EXEC mode with 'enable' commandAffected if CLI access is granted to any authenticated user, indicating the attack surface exists
-
Check for unauthorized or unexpected commands in SD-WAN CLI historyReview command history via 'show history' within SD-WAN CLI mode, or check system logs with 'show logging' for suspicious command patterns involving shell execution or unusual privilege escalationAffected if Commands observed contain shell operators (such as ';', '|', '$', or backticks) or commands outside normal SD-WAN operations
-
Inspect for signs of root-level command executionRun 'show sdwan software' or 'show sdwan system status' and compare against known-good baselines; also review 'show processes cpu history' for unusual activityAffected if Processes or software states indicate execution of commands that should not be issued through SD-WAN CLI
A user is affected if their Cisco IOS XE device has SD-WAN functionality enabled and CLI access is available to authenticated attackers, regardless of version since all versions are vulnerable.
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 · scopedRestrict CLI and management shell access to trusted, authorized users only; apply Cisco's official patch when available; monitor for suspicious command activity.
Obtain the specific fixed release from Cisco's security advisory for CVE-2023-20035 - check sec.cloudapps.cisco.com for the exact version number
- Check the Cisco Security Advisory (sec.cloudapps.cisco.com) for this CVE to identify the specific fixed release version
- Contact Cisco TAC or access the Cisco software download page to obtain the fixed IOS XE SD-WAN release
- Plan the upgrade during a maintenance window as the device may require a reload
- Back up the current device configuration before performing the upgrade
- Upload the new IOS XE SD-WAN software image to the device
- Verify the image integrity using the checksum provided by Cisco
- Reload the device to apply the new software version
- After reboot, verify the device is functioning correctly and the vulnerability is resolved by confirming the new software version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20035 — 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-2023-20035 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