Sd Wan OrchestratorApplication · VMware
CVE-2020-4000
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 · uneditedThe SD-WAN Orchestrator 3.3.2 prior to 3.3.2 P3, 3.4.x prior to 3.4.4, and 4.0.x prior to 4.0.1 allows for executing files through directory traversal. An authenticated SD-WAN Orchestrator user is able to traversal directories which may lead to code execution of files.
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 confidenceVMware SD-WAN Orchestrator contains a directory traversal vulnerability where authenticated users can manipulate file paths using traversal sequences (e.g., ../) to access files outside the intended directory and potentially execute arbitrary code. This stems from insufficient input validation on file path parameters in the web interface.
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 OrchestratorApplication
>= 3.4.0, < 3.4.4>= 4.0.0, < 4.0.1= 3.3.2CVSS 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.
-
Determine SD-WAN Orchestrator versionLog into the SD-WAN Orchestrator web interface and navigate to the Administration or System settings section to locate the version information. Alternatively, check the login page footer or about page for the exact version number.Affected if The installed version matches one of the following: 3.3.2, or any version >= 3.4.0 but < 3.4.4, or any version >= 4.0.0 but < 4.0.1
-
Verify management interface exposureDetermine if the SD-WAN Orchestrator management interface is accessible from untrusted networks by reviewing firewall rules, VPN policies, or network segmentation configurations that control access to the Orchestrator IP or hostname on the management port (typically 443).Affected if The management interface is reachable from networks outside the trusted administrative zone, increasing exposure to authenticated attackers.
-
Confirm user authentication is activeVerify that the web-based management interface is configured with active user accounts. Check if local users, LDAP integration, or other authentication methods are enabled in the Orchestrator authentication settings.Affected if User authentication is enabled and active, which is required for an attacker to exploit this vulnerability as an authenticated user.
-
Identify web interface endpoint accessibilityReview web server logs or proxy configurations to determine if the Orchestrator web API endpoints that accept file path parameters are exposed. These typically include endpoints related to file uploads, downloads, or configuration imports.Affected if The web interface API endpoints accepting file path parameters are accessible to authenticated users.
A user is affected if the SD-WAN Orchestrator runs an affected version (3.3.2, 3.4.x before 3.4.4, or 4.0.x before 4.0.1), has its management interface network-accessible, and maintains active user authentication that could be leveraged by an attacker.
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 data3.4.44.0.1
Apply vendor-provided patches: upgrade to SD-WAN Orchestrator 3.3.2 P3, 3.4.4, 4.0.1 or later. Until patched, restrict network access to the management interface and minimize the number of privileged users.
Fix this in Sd Wan Orchestrator
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4000 — 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-4000 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