dbcve.org
Catalyst Sd Wan ManagerApplication · Cisco

CVE-2022-20696

HIGH · 8.8 CVSS v3.1 Published 2022-09-08
Fix available
A fix is available. Upgrade to 20.6.4 / 20.9.1 or later.
See remediation →
93/100
Remediation priority · Urgent
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 the binding configuration of Cisco SD-WAN vManage Software containers could allow an unauthenticated, adjacent attacker who has access to the VPN0 logical network to also access the messaging service ports on an affected system. This vulnerability exists because the messaging server container ports on an affected system lack sufficient protection mechanisms. An attacker could exploit this vulnerability by connecting to the messaging service ports of the affected system. To exploit this vulnerability, the attacker must be able to send network traffic to interfaces within the VPN0 logical network. This network may be restricted to protect logical or physical adjacent networks, depending on device deployment configuration. A successful exploit could allow the attacker to view and inject messages into the messaging service, which can cause configuration changes or cause the system to reload.

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 containers have messaging service ports exposed without adequate protection due to insufficient binding configuration. An adjacent attacker with VPN0 network access can connect to these exposed messaging service ports, allowing unauthorized viewing and injection of messages that can trigger configuration changes or system reloads.

MitigationRestrict access to messaging service ports by implementing proper network segmentation or firewall rules on the VPN0 logical network, and update container binding configurations to limit port exposure to authorized management interfaces only.

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, < 20.9.1
Sd Wan VmanageApplication
Affected:< 20.6.4

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

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

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

  1. Identify installed vManage version
    Run 'show version' or access the vManage admin UI to view the installed software version
    Affected if The version is Cisco Catalyst SD-WAN Manager >= 20.7 and < 20.9.1, OR Cisco SD-WAN vManage < 20.6.4
  2. Verify messaging service port exposure
    Use netstat or similar network utility to list listening ports on the vManage container, specifically looking for messaging service ports typically used for inter-container communication
    Affected if Messaging service ports are bound to VPN0 or accessible from the VPN0 network interface rather than being restricted to localhost or management-only interfaces
  3. Inspect container binding configuration
    Examine the container runtime configuration or docker-compose files for the messaging service to determine which network interfaces the ports are bound to
    Affected if The binding configuration allows connections from VPN0 network rather than restricting to authorized management interfaces only
  4. Verify network segmentation
    Review firewall rules, access control lists, or network policies that control access to the messaging service ports from VPN0
    Affected if There are no effective restrictions preventing adjacent attackers on VPN0 from reaching the messaging service ports

A user is affected if their vManage version falls within the affected ranges AND the messaging service ports are exposed to the VPN0 network without proper access controls.

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.4 / 20.9.1 or later
Fixed in 20.6.420.9.1
Interim mitigation

Restrict access to messaging service ports by implementing proper network segmentation or firewall rules on the VPN0 logical network, and update container binding configurations to limit port exposure to authorized management interfaces only.

Recommended fix High confidence

Cisco Catalyst SD WAN Manager: 20.9.1 or later | Cisco SD WAN Vmanage: 20.6.4 or later

  1. Identify the current version of Cisco SD-WAN vManage running using the administration UI or CLI
  2. For Catalyst SD WAN Manager: Upgrade to version 20.9.1 or later
  3. For SD WAN Vmanage: Upgrade to version 20.6.4 or later
  4. After upgrade, verify the messaging service ports are no longer exposed to VPN0 logical network
  5. Confirm the system is running the fixed release
Caveat Review Cisco SD-WAN release notes for upgrade considerations and potential compatibility impacts before proceeding

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

Fix this in Catalyst Sd Wan Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,870
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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