dbcve.org
Sd Wan OrchestratorApplication · VMware

CVE-2020-3984

MEDIUM · 6.5 CVSS v3.1 Published 2020-11-24
Fix available
A fix is available. Upgrade to 3.4.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The SD-WAN Orchestrator 3.3.2 prior to 3.3.2 P3 and 3.4.x prior to 3.4.4 does not apply correct input validation which allows for SQL-injection. An authenticated SD-WAN Orchestrator user may exploit a vulnerable API call using specially crafted SQL queries which may lead to unauthorized data access.

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 confidence

SQL injection vulnerability in SD-WAN Orchestrator's API allows authenticated users to execute specially crafted SQL queries through a vulnerable API call, leading to unauthorized data access. Affected versions are 3.3.2 prior to 3.3.2 P3 and 3.4.x prior to 3.4.4.

MitigationUpgrade to SD-WAN Orchestrator version 3.3.2 P3 or 3.4.4 or later to apply the vendor patch. If immediate upgrade is not possible, implement strict input validation and least-privilege database accounts as compensating controls.

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
Affected:>= 3.4.0, < 3.4.4= 3.3.2

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SD-WAN Orchestrator version
    Access the Orchestrator admin interface or check the system information page. Alternatively, query the API endpoint that returns version information (typically /api/v1/system/info or similar). Compare the displayed version to the affected ranges: 3.3.2 (all versions prior to P3) and 3.4.0 through 3.4.3.
    Affected if The installed version is 3.3.2 (any build before P3) or falls between 3.4.0 and 3.4.3 inclusive.
  2. Verify API endpoint accessibility
    Confirm that the SD-WAN Orchestrator API is reachable from network locations where untrusted users could operate. Attempt to access the API base URL (typically https://<orchestrator-host>/api/v1/) from an authorized client to verify it responds.
    Affected if The API endpoint is exposed to users who are not explicitly trusted or authorized.
  3. Confirm API authentication configuration
    Review the SD-WAN Orchestrator authentication settings to determine whether the vulnerable API call requires authentication. Verify if the specific endpoint allowing the SQL injection accepts requests from authenticated users only or if authentication enforcement can be bypassed.
    Affected if The API endpoint permits authenticated user access without additional compensating controls such as strict input validation or least-privilege database accounts.
  4. Review database account privileges
    Examine the database credentials used by the Orchestrator application. Determine whether the database user associated with the API functionality operates with elevated privileges beyond what is strictly required for normal application operations.
    Affected if The Orchestrator database account has excessive privileges (such as DROP, DELETE, or broad SELECT access beyond the application schema) that could enable data exfiltration or modification through SQL injection.

A user is affected if the SD-WAN Orchestrator version is 3.3.2 prior to P3 or between 3.4.0 and 3.4.3, and the API is accessible to authenticated users without compensating controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.4.4 or later
Fixed in 3.4.4
Interim mitigation

Upgrade to SD-WAN Orchestrator version 3.3.2 P3 or 3.4.4 or later to apply the vendor patch. If immediate upgrade is not possible, implement strict input validation and least-privilege database accounts as compensating controls.

Fix this in Sd Wan Orchestrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3984 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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