Sd Wan FirmwareOperating system · Cisco
CVE-2020-3379
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 Cisco SD-WAN Solution Software could allow an authenticated, local attacker to elevate privileges to Administrator on the underlying operating system. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending a crafted request to an affected system. A successful exploit could allow the attacker to gain administrative privileges.
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 confidenceThis is a local privilege escalation vulnerability in Cisco SD-WAN Solution Software. An authenticated attacker with local system access can send a crafted request that bypasses input validation checks, allowing elevation to Administrator privileges on the underlying operating system.
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
Sd Wan FirmwareOperating system
< 18.3.0
Vbond OrchestratorApplication
all versions
Vsmart ControllerApplication
all 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 if Cisco SD-WAN software is runningLog into the device CLI or admin interface and run 'show version' or check the system dashboard to confirm the presence of Cisco SD-WAN components such as vbond, vsmart, or vedge.Affected if Any of these SD-WAN components (vbond orchestrator, vsmart controller, or SD-WAN firmware) are installed and running.
-
Determine the SD-WAN firmware versionExecute 'show version' or 'show software version' from the CLI prompt on SD-WAN vedge or cEdge devices to retrieve the installed firmware version number.Affected if The firmware version is displayed as a number lower than 18.3.0 (for example, 18.2.x, 18.1.x, or earlier).
-
Check the Vbond Orchestrator versionAccess the Vbond Orchestrator admin interface or use 'show version' via SSH to identify the Vbond software version.Affected if Any version of Vbond Orchestrator is found, as all versions are affected per the advisory.
-
Check the Vsmart Controller versionAccess the Vsmart Controller via CLI or admin UI and retrieve the software version using 'show version' or checking the system information page.Affected if Any version of Vsmart Controller is found, as all versions are affected per the advisory.
The environment is affected if any Cisco SD-WAN component is present: SD-WAN firmware version below 18.3.0, or any version of Vbond Orchestrator or Vsmart Controller.
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 data18.3.0
Apply the vendor patch from Cisco for this vulnerability. As a high-severity local privilege escalation, prioritize patching systems with any local user access.
Fix this in Sd Wan Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3379 — 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-2020-3379 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