Catalyst Sd Wan ManagerApplication · Cisco

CVE-2021-1506

HIGH · 7.2 CVSS v3.1 Published 2021-05-06
Fix available
A fix is available. Upgrade to 20.3.3 / 20.4.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Multiple vulnerabilities in Cisco SD-WAN vManage Software could allow an unauthenticated, remote attacker to execute arbitrary code or gain access to sensitive information, or allow an authenticated, local attacker to gain escalated privileges or gain unauthorized access to the application. For more information about these vulnerabilities, see the Details section of this advisory.

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

Multiple vulnerabilities in Cisco SD-WAN vManage Software allow unauthenticated remote attackers to potentially execute arbitrary code or access sensitive information, while authenticated local attackers may achieve privilege escalation or unauthorized application access.

MitigationApply Cisco's official patches for SD-WAN vManage per the referenced advisory; restrict network access to management interfaces and follow least-privilege principles for local accounts.

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.4.1>= 20.5, < 20.5.1
Sd Wan VmanageApplication
Affected:< 20.3.3

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the installed Cisco SD-WAN vManage version
    Access the vManage admin UI or use the 'show version' CLI command on the vManage appliance to retrieve the exact software version number
    Affected if The version is < 20.3.3, OR >= 20.4 and < 20.4.1, OR >= 20.5 and < 20.5.1
  2. Confirm the product is Cisco SD-WAN vManage or Cisco Catalyst SD-WAN Manager
    Verify the product name via the vManage web interface header or CLI output showing 'vManage' or 'Cisco Catalyst SD-WAN Manager'
    Affected if The product is either Cisco SD-WAN vManage or Cisco Catalyst SD-WAN Manager and falls within the version ranges in step 1
  3. Assess exposure of the vManage management interface
    Check network configuration to determine if TCP ports 443, 8443, or other management ports on vManage are accessible from untrusted networks or the internet
    Affected if Management interface is directly exposed to untrusted networks (enables the unauthenticated attack vector)
  4. Review local user accounts on vManage
    Use the vManage Administration > Users section in the web UI or the 'show users' CLI command to list all locally configured user accounts
    Affected if Any local user accounts exist (enables the authenticated local attack vector for privilege escalation)

A user is affected if they are running Cisco SD-WAN vManage or Cisco Catalyst SD-WAN Manager with a version in < 20.3.3, >= 20.4 to < 20.4.1, or >= 20.5 to < 20.5.1, with the management interface network-accessible or with local accounts configured.

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.

From vendor data
Upgrade available Upgrade to 20.3.3 / 20.4.1 / 20.5.1 or later
Fixed in 20.3.320.4.120.5.1
Interim mitigation

Apply Cisco's official patches for SD-WAN vManage per the referenced advisory; restrict network access to management interfaces and follow least-privilege principles for local accounts.

Fix this in Catalyst Sd Wan Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-1506 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