dbcve.org
Sd WanApplication · Cisco

CVE-2022-20844

MEDIUM · 5.3 CVSS v3.1 Published 2022-09-30
Fix available
A fix is available. Upgrade to 20.6.3 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 using a default static username and password combination. 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 · moderate confidence

This is a default credential vulnerability in Cisco SD-AVC running on Cisco vManage. An unauthenticated, remote attacker can access the SD-AVC GUI using a hardcoded default username and password combination, allowing them to view managed device names, SD-AVC logs, and DNS server IP addresses.

MitigationChange the default static credentials immediately and restrict GUI access using network segmentation, firewalls, or VPN access controls to prevent exposure to untrusted networks.

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.4.1, < 20.6.3= 20.3.4.1= 20.3.4.2= 20.3.5= 20.7.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 the Cisco vManage version
    Access the vManage administrative interface or use the CLI command 'show version' to retrieve the installed software version.
    Affected if The version falls within the affected ranges: >= 20.4.1 and < 20.6.3, or equals 20.3.4.1, 20.3.4.2, 20.3.5, or 20.7.1
  2. Confirm SD-AVC feature is enabled
    Log into vManage and navigate to the SD-AVC configuration section, or use the CLI to check if SD-AVC is active.
    Affected if SD-AVC is enabled and running on the vManage instance
  3. Verify if default credentials are still in use
    Check the SD-AVC user accounts configuration. The hardcoded default credentials should have been changed. If the original default username and password remain unchanged, the system is vulnerable.
    Affected if The default username and password for SD-AVC have not been modified from their hardcoded values
  4. Assess GUI network exposure
    Determine if the SD-AVC GUI interface is accessible from untrusted networks by reviewing firewall rules, access lists, or network segmentation configurations.
    Affected if The SD-AVC GUI is reachable from untrusted or external networks without adequate access controls

The system is affected if it runs a vulnerable Cisco SD-WAN version with SD-AVC enabled and the hardcoded default credentials remain unchanged, especially when the GUI is exposed to untrusted networks.

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.3 or later
Fixed in 20.6.3
Interim mitigation

Change the default static credentials immediately and restrict GUI access using network segmentation, firewalls, or VPN access controls to prevent exposure to untrusted networks.

Recommended fix Moderate confidence

Cisco vManage version 20.6.3 or later (Cisco SD-AVC)

  1. 1. Identify the current Cisco vManage version by navigating to the Administration > System Settings > Upgrade page in the vManage GUI
  2. 2. Confirm the exact SD-AVC version affected by checking the Cisco SD-AVC release notes for your current version
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Backup the current vManage configuration and verify backup integrity
  5. 5. Download Cisco vManage version 20.6.3 or later from the Cisco Software Download center (software.cisco.com)
  6. 6. Upload the upgrade file to vManage via the Administration > Software Upgrade page
  7. 7. Initiate the upgrade and monitor the process for completion
  8. 8. After upgrade, verify that the default static credentials vulnerability is resolved by confirming SD-AVC GUI access requires proper authentication
Caveat Review Cisco SD-AVC release notes for 20.6.3 for any configuration or behavioral changes; ensure compatibility with existing SD-WAN deployment 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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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