dbcve.org
Sd Wan Vedge RouterWeb browser · Cisco

CVE-2022-20717

MEDIUM · 5.5 CVSS v3.1 Published 2022-04-15
Fix available
A fix is available. Upgrade to after 20.6 or later.
See remediation →
57/100
Remediation priority · Elevated
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 NETCONF process of Cisco SD-WAN vEdge Routers could allow an authenticated, local attacker to cause an affected device to run out of memory, resulting in a denial of service (DoS) condition. This vulnerability is due to insufficient memory management when an affected device receives large amounts of traffic. An attacker could exploit this vulnerability by sending malicious traffic to an affected device. A successful exploit could allow the attacker to cause the device to crash, resulting in a DoS condition.

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

A vulnerability in the NETCONF process of Cisco SD-WAN vEdge Routers allows an authenticated, local attacker to exhaust device memory by sending malicious traffic, causing the device to crash and result in a denial of service.

MitigationRestrict NETCONF access to trusted administrators only, implement traffic rate limiting on affected devices, and deploy memory usage monitoring to detect exhaustion before crash.

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 Wan Vedge RouterWeb browser
Affected:<= 20.6= 20.7

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the installed software version
    Run 'show version' or 'show software' command on the vEdge router CLI to obtain the current software version
    Affected if The version number is 20.6 or earlier, or exactly 20.7
  2. Confirm NETCONF is enabled
    Run 'show netconf-yang status' or check the configuration with 'show configuration netconf' to see if NETCONF service is active
    Affected if NETCONF is enabled and running on the device
  3. Verify NETCONF access is unrestricted
    Review the NETCONF access control list or service configuration with 'show configuration system netconf' to see if any IP or user restrictions are applied
    Affected if NETCONF has no access restrictions or is accessible from untrusted networks
  4. Check device memory utilization
    Run 'show system resources' or 'show memory' to inspect current memory usage levels
    Affected if Memory utilization is abnormally high or approaching exhaustion
  5. Examine logs for NETCONF-related crashes
    Run 'show log' or 'show crashlog' looking for NETCONF process restarts, memory allocation failures, or unexpected device reloads
    Affected if Logs indicate NETCONF process failures, memory exhaustion events, or unexplained device crashes

The device is affected if it runs Cisco SD-WAN vEdge software version 20.6 or earlier (or exactly 20.7) with NETCONF enabled and accessible, and exhibits memory exhaustion symptoms or NETCONF-related crashes.

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 a release after 20.6
Interim mitigation

Restrict NETCONF access to trusted administrators only, implement traffic rate limiting on affected devices, and deploy memory usage monitoring to detect exhaustion before crash.

Recommended fix Moderate confidence

Cisco SD-WAN vEdge Router version 20.8 or later

  1. 1. Identify the current Cisco SD-WAN vEdge Router software version using the 'show version' command
  2. 2. Download the fixed software release from Cisco (version 20.8 or later) from the Cisco software download center
  3. 3. Upload the new software image to the device or controller
  4. 4. Follow Cisco's standard upgrade procedure for SD-WAN vEdge Routers, which typically involves using the vManage software deployment process
  5. 5. After upgrade, verify the device is functioning properly and the NETCONF process is running normally
  6. 6. Confirm the vulnerability is resolved by checking that the device no longer exhausts memory under large traffic conditions
Caveat Standard SD-WAN upgrade considerations apply - ensure compatibility with vManage and other SD-WAN components before upgrading

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

Fix this in Sd Wan Vedge Router Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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