Sd Wan OrchestratorApplication · VMware
CVE-2020-4001
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, 3.4.x, and 4.0.x has default passwords allowing for a Pass-the-Hash Attack. SD-WAN Orchestrator ships with default passwords for predefined accounts which may lead to to a Pass-the-Hash attack.
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 confidenceThe SD-WAN Orchestrator versions 3.3.2, 3.4.x, and 4.0.x ships with predefined accounts that have default passwords. Attackers can perform a Pass-the-Hash attack by using the password hash directly for authentication, bypassing the need to crack or obtain the plaintext password.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Determine the installed SD-WAN Orchestrator versionLog into the SD-WAN Orchestrator web interface and navigate to the About page, or use the CLI command 'show version' to retrieve the installed version number.Affected if The installed version is 3.3.2, or falls within 3.4.0-3.4.4, or falls within 4.0.0-4.0.1.
-
Identify predefined default accountsNavigate to the User Management or Administration section in the SD-WAN Orchestrator web UI, or use the CLI command to list all local user accounts. Look for accounts that are pre-configured by default such as 'admin', 'operator', or 'support'.Affected if Predefined system accounts exist in the user database.
-
Verify if default passwords have been changedCheck the password last-change timestamp for each predefined account in the user management interface, or review authentication audit logs for signs of original default password usage. Compare current password hashes against known default password hashes for these accounts if accessible.Affected if Any predefined account still retains its factory default password or the password has never been changed since initial installation.
-
Check for unused default accountsReview the list of enabled predefined accounts and identify any that are not actively used for legitimate administrative or operational purposes.Affected if Unused predefined accounts remain enabled in the system.
A system is affected if it runs a vulnerable SD-WAN Orchestrator version (3.3.2, 3.4.0-3.4.4, or 4.0.0-4.0.1) AND has predefined accounts with unchanged default passwords.
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 dataImmediately change all default passwords on predefined accounts to strong, unique passwords following organizational password policies. Disable any unused default accounts.
Fix this in Sd Wan Orchestrator
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4001 — 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-4001 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