Catalyst Sd Wan ManagerApplication · Cisco
CVE-2021-1284
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 · uneditedA vulnerability in the web-based messaging service interface of Cisco SD-WAN vManage Software could allow an unauthenticated, adjacent attacker to bypass authentication and authorization and modify the configuration of an affected system. To exploit this vulnerability, the attacker must be able to access an associated Cisco SD-WAN vEdge device. This vulnerability is due to insufficient authorization checks. An attacker could exploit this vulnerability by sending crafted HTTP requests to the web-based messaging service interface of an affected system. A successful exploit could allow the attacker to gain unauthenticated read and write access to the affected vManage system. With this access, the attacker could access information about the affected vManage system, modify the configuration of the system, or make configuration changes to devices that are managed by the system.
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 confidenceInsufficient authorization checks in Cisco SD-WAN vManage's web-based messaging service interface allow an unauthenticated, adjacent attacker with access to an associated vEdge device to bypass authentication via crafted HTTP requests, granting unauthenticated read/write access to the vManage system for information disclosure and configuration manipulation.
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.1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed vManage versionUse the CLI command 'show version' or access the vManage administrative interface to view the software version. Compare the version number against the affected ranges: < 20.3.1, or >= 20.4 to < 20.4.1, or >= 20.5 to < 20.5.1Affected if The installed version falls within any of the affected ranges (< 20.3.1, >= 20.4 to < 20.4.1, >= 20.5 to < 20.5.1)
-
Confirm vEdge device connectivityUse the vManage CLI or UI to list connected vEdge devices. Verify if any vEdge devices are currently registered and communicating with the vManage instanceAffected if vEdge devices are connected and actively communicating with the vManage system, creating the adjacent network attack path described in the CVE
-
Verify the web-based messaging service interface statusCheck the vManage service configuration to determine if the web-based messaging service interface is enabled and accessible. Review network service listeners or HTTP service bindingsAffected if The web-based messaging service interface is exposed and enabled on the vManage system
-
Review authentication logs for anomalous requestsExamine vManage authentication and access logs for unusual HTTP requests, particularly those originating from vEdge device IP ranges that bypass normal authentication flows or show unexpected authorization behaviorAffected if Logs contain authentication bypass attempts, unauthorized HTTP requests from vEdge device sources, or successful requests without proper credentials
You are affected if your vManage version is < 20.3.1, >= 20.4 and < 20.4.1, or >= 20.5 and < 20.5.1, AND you have vEdge devices connected with the web-based messaging service interface enabled.
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.
dbcve · scoped20.3.120.4.120.5.1
Apply Cisco's security patches for this vulnerability. Additionally, restrict network access to vEdge devices and implement network segmentation to limit the attack surface for adjacent attackers.
Upgrade to Cisco SD-WAN vManage version 20.3.1, 20.4.1, 20.5.1, or later stable release
- 1. Identify the current version of Cisco SD-WAN vManage by accessing the administration settings in the vManage web interface
- 2. For systems running version 20.3.x or earlier, upgrade to version 20.3.1 or later
- 3. For systems running version 20.4.x (>=20.4, <20.4.1), upgrade to version 20.4.1
- 4. For systems running version 20.5.x (>=20.5, <20.5.1), upgrade to version 20.5.1
- 5. After upgrade, verify the system is running the fixed version and confirm the web-based messaging service interface is functioning correctly
- 6. Review system logs for any signs of exploitation attempts
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Catalyst Sd Wan Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1284 — 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-1284 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