CVE-2021-1273
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 · uneditedMultiple vulnerabilities in Cisco SD-WAN products could allow an unauthenticated, remote attacker to execute denial of service (DoS) 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 confidenceMultiple vulnerabilities in Cisco SD-WAN products allow an unauthenticated, remote attacker to execute denial of service (DoS) attacks against affected devices. The vulnerabilities likely involve improper input validation or resource management in the SD-WAN software stack, enabling attackers to crash or saturate the device without authentication.
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 dataall versions= 18.3.5= 18.3.8= 18.4.1= 18.4.4= 18.4.5= 19.2.0= 19.2.1= 19.2.2= 19.2.99= 20.1.0all versionsall versionsall versionsCVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SD-WAN product typeLog into the device CLI or management interface and run 'show version' or check the SD-WAN Manager console to determine which SD-WAN component is running (IOS XE SD-WAN, SD-WAN Firmware, vSmart Controller, vBond Orchestrator, or Catalyst SD-WAN Manager)Affected if The device is running any Cisco SD-WAN component (IOS XE SD-WAN, SD-WAN Firmware, vSmart, vBond, or SD-WAN Manager)
-
Check Cisco IOS XE SD-WAN versionRun 'show version' on the IOS XE SD-WAN device and note the IOS XE release numberAffected if The device is running any version of Cisco IOS XE SD-WAN (all versions are affected)
-
Check SD-WAN Firmware versionRun 'show sdwan version' or access the vManage/vSmart/vBond CLI and check the firmware release using 'show version' or 'about' commandAffected if The firmware version matches: 18.3.5, 18.3.8, 18.4.1, 18.4.4, 18.4.5, 19.2.0, 19.2.1, 19.2.2, 19.2.99, or 20.1.0
-
Check vSmart/vBond/SD-WAN Manager versionAccess the controller CLI or SD-WAN Manager interface and run 'show version' or check the About section in the web UIAffected if The device is running any version of Cisco SD-WAN vSmart Controller, vBond Orchestrator, or Catalyst SD-WAN Manager (all versions are affected)
-
Verify network exposure of SD-WAN interfacesReview the device configuration for 'wanip' or interface bindings using 'show sdwan interface' or check access control lists; determine if management or SD-WAN control plane interfaces are reachable from untrusted networksAffected if SD-WAN management or control interfaces are exposed to untrusted networks without authentication barriers
If the environment contains any Cisco IOS XE SD-WAN, SD-WAN Firmware (listed versions), vSmart Controller, vBond Orchestrator, or Catalyst SD-WAN Manager, and these interfaces are network-accessible, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Cisco SD-WAN patches or updates as specified in the Cisco advisory. Implement network segmentation and access controls to limit exposure to unauthenticated attackers until patches are applied.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1273 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-1273 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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