dbcve.org
Catalyst Sd Wan ManagerApplication · Cisco

CVE-2022-20735

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-15
Fix available
A fix is available. Upgrade to 20.6.1 or later.
See remediation →
72/100
Remediation priority · Elevated
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 · high confidence

Cisco SD-WAN vManage Software contains a cross-site request forgery (CSRF) vulnerability in its web-based management interface due to insufficient CSRF protection mechanisms. An unauthenticated remote attacker can exploit this by tricking an authenticated user into clicking a malicious link, allowing arbitrary actions with the user's privilege level including system configuration changes and account deletion.

MitigationApply the vendor patch released by Cisco for this vulnerability. Additionally, implement temporary compensating controls such as educating users about suspicious links and monitoring for unauthorized configuration changes until the patch can be deployed.

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.7
Sd Wan VmanageApplication
Affected:< 20.6.1

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 version
    Access the vManage CLI and run 'show version' or use the web UI footer/version page to determine the installed software version.
    Affected if The installed version is 20.7 or is less than 20.6.1 (for example, 20.6.0, 20.5.x, earlier releases).
  2. Verify web-based management interface is enabled
    Confirm that the vManage web UI (typically on port 443) is accessible and actively used for administration.
    Affected if The web management interface is enabled and accessible to users.
  3. Check if anti-CSRF tokens are present in web forms
    Log into the vManage web interface and inspect HTML forms (via browser developer tools or proxy) to determine if each form submission includes a unique anti-CSRF token parameter.
    Affected if Forms lack anti-CSRF tokens or use predictable/static token values.

You are affected if your Cisco SD-WAN vManage version is exactly 20.7 or below 20.6.1 AND the web-based management interface is enabled.

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.1 or later
Fixed in 20.6.1
Interim mitigation

Apply the vendor patch released by Cisco for this vulnerability. Additionally, implement temporary compensating controls such as educating users about suspicious links and monitoring for unauthorized configuration changes until the patch can be deployed.

Recommended fix Moderate confidence

Upgrade to Cisco SD-WAN vManage version 20.6.1 or later

  1. 1. Back up the current vManage configuration before initiating any upgrade.
  2. 2. Download the fixed version of Cisco SD-WAN vManage software (version 20.6.1 or later) from Cisco's official software download portal.
  3. 3. Upload the new software image to the vManage server using the administration interface.
  4. 4. Initiate the upgrade process through the vManage web interface or CLI.
  5. 5. Verify the upgrade completed successfully and confirm all services are running.
  6. 6. Test that CSRF protections are now properly enforced by verifying the application includes anti-CSRF tokens in requests.
Caveat Review Cisco release notes for version 20.6.1 for any configuration or compatibility changes before upgrading

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

Fix this in Catalyst Sd Wan Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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