dbcve.org
Sd WanApplication · Cisco

CVE-2023-20113

HIGH · 8.1 CVSS v3.1 Published 2023-03-23
Fix available
A fix is available. Upgrade to 20.6.5 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 web-based management interface of Cisco SD-WAN vManage Software could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack on an affected system. This vulnerability is due to insufficient CSRF protections for the web-based management interface on an affected system. An attacker could exploit this vulnerability by persuading a user of the interface to click a malicious link. A successful exploit could allow the attacker to perform arbitrary actions with the privilege level of the affected user. These actions could include modifying the system configuration and deleting accounts.

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

A CSRF vulnerability in Cisco SD-WAN vManage's web-based management interface allows unauthenticated remote attackers to trick authenticated users into executing unintended actions by clicking malicious links. Successful exploitation grants the attacker the victim's privilege level, enabling system configuration modifications and account deletion.

MitigationApply the Cisco-provided patch for this vulnerability. In the interim, educate users to avoid clicking untrusted links and consider implementing additional CSRF countermeasures at the network perimeter if feasible.

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
Sd WanApplication
Affected:< 20.6.5= 20.8.0= 20.9.0

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

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

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

  1. Identify Cisco SD-WAN vManage installation
    Check for the vManage service or process running on the system. On Linux, run 'ps aux | grep vmanage' or check for the vmanage process. On the device, use 'show version' or check the software version through the CLI if available.
    Affected if Cisco SD-WAN vManage software is installed and running
  2. Determine the installed vManage version
    Access the vManage web UI and navigate to Administration > Software or use the CLI command 'request software version' or check the '/opt/vmanage/version' file if accessible. Alternatively, check the software release notes or the vManage dashboard for the version number.
    Affected if The installed version is less than 20.6.5, or exactly 20.8.0, or exactly 20.9.0
  3. Verify the web-based management interface is enabled
    Check if the vManage web UI port (default 8443 or 443) is listening and accessible. Use 'netstat -tlnp | grep -E "(8443|443)"' or 'ss -tlnp | grep -E "(8443|443)"' to verify the web service is bound to an interface.
    Affected if The vManage web management interface is exposed and listening on a network interface
  4. Confirm authentication is required for web UI access
    Verify that the web-based management interface requires authentication by attempting to access it or checking the authentication settings in vManage's configuration. CSRF requires an authenticated session to exploit.
    Affected if The web interface accepts authenticated sessions, meaning users can log in and maintain active sessions

The environment is affected if Cisco SD-WAN vManage is running with a version matching < 20.6.5, = 20.8.0, or = 20.9.0, and the web-based management interface is accessible and accepts authenticated users.

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.5 or later
Fixed in 20.6.5
Interim mitigation

Apply the Cisco-provided patch for this vulnerability. In the interim, educate users to avoid clicking untrusted links and consider implementing additional CSRF countermeasures at the network perimeter if feasible.

Recommended fix Moderate confidence

Upgrade to vManage version 20.6.5.1 or later (20.10.x or latest stable release)

  1. 1. Identify the current installed version of Cisco SD-WAN vManage by logging into the vManage web interface and navigating to Administration > System Settings > Software Repository, or by running 'show version' via CLI.
  2. 2. Confirm the running version against the affected versions: anything below 20.6.5, or exactly 20.8.0 or 20.9.0.
  3. 3. Schedule a maintenance window as the upgrade will require a system reboot and may cause brief downtime.
  4. 4. Backup the current vManage configuration using the web interface (Administration > Backup & Restore) or CLI before proceeding.
  5. 5. Download the fixed software version from Cisco (contact Cisco TAC or access the Cisco software download portal with valid service contract).
  6. 6. Upload the new software image via vManage: navigate to Maintenance > Software Upgrade > Upload Software Image.
  7. 7. Initiate the upgrade: select the uploaded image and click 'Install Upgrade', choosing 'Reboot' as the install type.
  8. 8. After the upgrade completes, verify the new version by logging into vManage and confirming the version number in the About section.
Caveat Review Cisco SD-WAN release notes for any configuration changes or deprecated features 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 Sd Wan Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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