Catalyst Sd Wan ManagerApplication · Cisco
CVE-2021-1275
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 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 confidenceMultiple vulnerabilities in Cisco SD-WAN vManage Software allow an unauthenticated remote attacker to execute arbitrary code or access sensitive information, and an authenticated local attacker to gain elevated privileges or unauthorized application access.
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
>= 20.4, < 20.4.1>= 20.5, < 20.5.1
Sd Wan VmanageApplication
< 20.3.3CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Cisco SD-WAN vManage software versionLog into the vManage CLI and run 'show version' or access the web UI and navigate to Administration > Settings > Software Repository to view the current versionAffected if Version number is < 20.3.3, OR >= 20.4.0 and < 20.4.1, OR >= 20.5.0 and < 20.5.1
-
Confirm if the vManage API is exposed to unauthenticated accessReview vManage system settings under Administration > User Management > API Users, and check if API endpoints accept requests without valid authentication tokensAffected if API endpoints are accessible without requiring authentication (empty Bearer tokens or no token accepted)
-
Verify network exposure of the vManage management interfaceCheck firewall rules, ACLs, or network segmentation to determine if the vManage web interface (port 443) is reachable from untrusted network segments or the internetAffected if vManage management interface is directly accessible from untrusted networks without VPN, jump host, or proper ACL restrictions
The environment is affected if the installed vManage version falls within the vulnerable ranges AND the application is network-accessible to unauthenticated attackers.
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 data20.3.320.4.120.5.1
Apply Cisco-provided security patches for SD-WAN vManage software; prioritize patching the remote code execution vulnerabilities given the CVSS 7.5 severity and unauthenticated attack vector.
Fix this in Catalyst Sd Wan Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1275 — 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-1275 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