Ios Xe Sd WanOperating system · Cisco

CVE-2021-1300

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Multiple vulnerabilities in Cisco SD-WAN products could allow an unauthenticated, remote attacker to execute attacks against an affected device. 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 critical-severity vulnerabilities in Cisco SD-WAN software allow unauthenticated remote attackers to execute arbitrary attacks against affected devices.

MitigationApply vendor-supplied patches or updates for Cisco SD-WAN products as specified in the official Cisco security advisory.

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
Ios Xe Sd WanOperating system
Affected:all versions
Sd Wan FirmwareOperating system
Affected:= 18.3.8= 18.4.4= 19.2.1= 19.2.99
Sd Wan Vsmart Controller FirmwareOperating system
Affected:all versions
Catalyst Sd Wan ManagerApplication
Affected:all versions
Sd Wan Vbond OrchestratorApplication
Affected:all versions

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 Cisco SD-WAN product deployment
    Inventory network devices and identify any Cisco SD-WAN components (vBond, vSmart, vEdge, Cisco SD-WAN Manager, IOS-XE SD-WAN) in the environment. Check device model numbers and running software.
    Affected if Any Cisco SD-WAN product (vBond Orchestrator, vSmart Controller, vEdge, Catalyst SD-WAN Manager, or IOS-XE with SD-WAN) is deployed.
  2. Check IOS-XE SD-WAN version
    On Cisco IOS-XE devices with SD-WAN capability, run 'show version' or 'show sdwan version' to obtain the software version.
    Affected if The device runs Cisco IOS-XE SD-WAN (any version, as all versions are affected per the advisory).
  3. Check SD-WAN Firmware version
    On vEdge or SD-WAN edge devices, run 'show software' or check the firmware version via the vManage web interface under Device > Inventory.
    Affected if The firmware version matches exactly: 18.3.8, 18.4.4, 19.2.1, or 19.2.99.
  4. Check vSmart Controller version
    Run 'show version' on vSmart Controller or check via vManage under Controllers > vSmart.
    Affected if Any version of Cisco SD-WAN vSmart Controller firmware is running (all versions affected).
  5. Check vBond Orchestrator version
    Run 'show version' on vBond or check via vManage under Orchestrators.
    Affected if Any version of Cisco SD-WAN vBond Orchestrator is running (all versions affected).
  6. Verify SD-WAN feature is active
    Check that the SD-WAN control connection is established using 'show sdwan control connections' on IOS-XE or 'show control connections' on vEdge/vSmart.
    Affected if The SD-WAN feature is enabled and the device has active SD-WAN control plane connections, making it exploitable.

If any Cisco SD-WAN product (vBond, vSmart, vEdge, Catalyst SD-WAN Manager, or IOS-XE SD-WAN) is deployed and the SD-WAN feature is active, the environment is affected by CVE-2021-1300.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches or updates for Cisco SD-WAN products as specified in the official Cisco security advisory.

Fix this in Ios Xe Sd Wan 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 help mitigating

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-1300 — 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-1300 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