Sd Wan FirmwareOperating system · Cisco
CVE-2020-3381
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 management interface of Cisco SD-WAN vManage Software could allow an authenticated, remote attacker to conduct directory traversal attacks and obtain read and write access to sensitive files on a targeted system. The vulnerability is due to a lack of proper validation of files that are uploaded to an affected device. An attacker could exploit this vulnerability by uploading a crafted file to an affected system. An exploit could allow the attacker to view or modify arbitrary files on the targeted 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 · moderate confidenceDirectory traversal vulnerability in Cisco SD-WAN vManage web management interface allows authenticated attackers to read/write arbitrary files by uploading specially crafted files without proper validation. This grants remote attackers filesystem access on affected systems.
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>= 18.4.0, < 19.2.3>= 19.3.0, <= 20.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 the Cisco SD-WAN vManage firmware versionLog into the vManage CLI or navigate to Administration > Settings > Software Update to view the installed version number. Alternatively, use the command 'show version' in the vManage CLI.Affected if The installed version falls within: <= 18.3.0, >= 18.4.0 and < 19.2.3, or >= 19.3.0 and <= 20.1
-
Confirm the vManage web management interface is accessibleVerify that the vManage web UI (HTTPS on port 443 or configured port) is reachable from network segments that could contain an attacker. Check firewall rules and access lists governing inbound access to vManage.Affected if The web management interface is exposed to untrusted or insufficiently controlled network segments
-
Verify if file upload functionality exists and is accessibleIn the vManage web interface, navigate to Configuration > Files or Administration > Software Repository to check if file upload features are available to authenticated users.Affected if File upload capability is enabled and accessible to authenticated users in the web interface
-
Review authentication controls for vManage web accessCheck if the vManage web interface enforces strong authentication and if user account controls limit who can access file upload features.Affected if The vManage web interface allows file uploads from authenticated users without additional security restrictions on file paths or content validation
A user is affected if their Cisco SD-WAN vManage runs a firmware version within the listed ranges AND the web management interface with file upload functionality is accessible to authenticated but untrusted users.
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 data19.2.3
Apply Cisco security patches for CVE-2020-3381; restrict web management interface access to authorized personnel only; implement strict file upload validation and sanitize file paths to prevent traversal sequences.
Fix this in Sd Wan Firmware
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3381 — 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-3381 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