dbcve.org
Catalyst Sd Wan ManagerApplication · Cisco

CVE-2022-20830

MEDIUM · 5.3 CVSS v3.1 Published 2022-10-10
Fix available
A fix is available. Upgrade to 20.3.4.1 / 20.6.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 authentication mechanism of Cisco Software-Defined Application Visibility and Control (SD-AVC) on Cisco vManage could allow an unauthenticated, remote attacker to access the GUI of Cisco SD-AVC without authentication. This vulnerability exists because the GUI is accessible on self-managed cloud installations or local server installations of Cisco vManage. An attacker could exploit this vulnerability by accessing the exposed GUI of Cisco SD-AVC. A successful exploit could allow the attacker to view managed device names, SD-AVC logs, and SD-AVC DNS server IP addresses.

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

Authentication bypass vulnerability in Cisco SD-AVC (Software-Defined Application Visibility and Control) on Cisco vManage allows unauthenticated remote attackers to access the GUI interface. The vulnerability exists because the GUI is exposed on self-managed cloud or local server installations without proper authentication enforcement. Successful exploitation permits viewing of managed device names, SD-AVC logs, and SD-AVC DNS server IP addresses.

MitigationApply proper authentication controls to the SD-AVC GUI on self-managed cloud and local vManage installations; consult Cisco security advisories for specific patch or configuration guidance.

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.4, < 20.6.1= 20.7
Sd Wan VmanageApplication
Affected:>= 18.4, < 20.3.4.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 vManage version
    Run 'show version' or check the vManage admin UI for the installed software version number
    Affected if The version falls within >= 20.4 and < 20.6.1, equals 20.7 (for Cisco Catalyst SD-WAN Manager), or within >= 18.4 and < 20.3.4.1 (for Cisco SD-WAN vManage)
  2. Verify SD-AVC component is active
    Check if the Software-Defined Application Visibility and Control feature is enabled in the vManage system settings or configuration
    Affected if SD-AVC is enabled and running on the vManage instance
  3. Confirm deployment type
    Determine whether the vManage installation is a self-managed cloud deployment or on-premises local server, as opposed to a Cisco-hosted service
    Affected if The installation is self-managed cloud or local server rather than a fully managed Cisco-hosted deployment
  4. Test GUI authentication enforcement
    Attempt to access the SD-AVC GUI interface URL (typically /sdavc or /appmnt/sdavc) from an unauthenticated browser session or via curl without credentials
    Affected if The GUI interface is accessible without requiring authentication credentials

A user is affected if their vManage runs an affected version, SD-AVC is enabled, it is a self-managed deployment, and the GUI can be accessed without authentication.

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

Apply proper authentication controls to the SD-AVC GUI on self-managed cloud and local vManage installations; consult Cisco security advisories for specific patch or configuration guidance.

Recommended fix High confidence

Catalyst SD WAN Manager: 20.6.1 or later (20.8+ recommended); SD WAN vManage: 20.3.4.1 or later (20.4+ recommended)

  1. 1. Identify the currently installed Cisco vManage version by checking the system information or running 'show version' in the CLI
  2. 2. For Catalyst SD WAN Manager: Upgrade to version 20.6.1 or later (20.8 or newer recommended)
  3. 3. For SD WAN vManage: Upgrade to version 20.3.4.1 or later (20.4 or newer recommended)
  4. 4. Download the appropriate Cisco SD WAN software from Cisco.com (requires valid SMARTnet contract)
  5. 5. Follow Cisco's standard upgrade procedure for vManage: upload the .tar file to the vManage repository, then initiate the upgrade via the vManage GUI or CLI
  6. 6. After upgrade, verify the new version is installed and confirm the SD-AVC GUI now requires authentication
  7. 7. Review Cisco release notes for any additional post-upgrade configuration steps
Caveat Standard Cisco upgrade risks apply - ensure backups and maintenance windows are planned; some older browser versions may not be compatible with newer GUI

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

Fix this in Catalyst Sd Wan Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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