dbcve.org
Sd Wan Edge FirmwareOperating system · VMware

CVE-2023-20899

HIGH · 7.5 CVSS v3.1 Published 2023-07-06
Fix available
A fix is available. Upgrade to 4.5.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
VMware SD-WAN (Edge) contains a bypass authentication vulnerability. An unauthenticated attacker can download the Diagnostic bundle of the application under VMware SD-WAN Management.

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

VMware SD-WAN Edge contains an authentication bypass vulnerability that allows unauthenticated attackers to access and download the diagnostic bundle from the SD-WAN Management interface without proper credentials.

MitigationApply the vendor-supplied security patch for VMware SD-WAN. As an interim measure, restrict network access to the SD-WAN Management interface to trusted networks only and monitor for unauthorized access attempts.

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 Edge FirmwareOperating system
Affected:>= 4.5.0, < 4.5.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 the SD-WAN Edge firmware version
    Access the SD-WAN Orchestrator or Edge CLI and retrieve the firmware version. In the Orchestrator UI, navigate to the Edge summary page to view the current firmware version. Alternatively, use the CLI command 'show version' or check the Orchestrator under 'Edges > [Select Edge] > Device > System' to find the firmware version.
    Affected if The installed firmware version is >= 4.5.0 and < 4.5.2 (for example, 4.5.0 or 4.5.1).
  2. Confirm the SD-WAN Management interface is accessible
    Determine if the SD-WAN Management interface (typically on port 443/HTTPS) is exposed to untrusted networks. Check firewall rules, NAT configurations, or VPN settings that control access to the management IP/hostname of the SD-WAN Edge or Orchestrator.
    Affected if The management interface is reachable from networks outside of trusted internal networks, increasing the likelihood of exploitation.
  3. Review access logs for diagnostic bundle downloads
    Examine SD-WAN Orchestrator or Edge logs for requests to diagnostic bundle download endpoints, such as '/diagbundle' or similar export functions. Look for unauthenticated or unexpected download attempts, especially from external IP addresses.
    Affected if There are log entries showing diagnostic bundle downloads initiated by unauthenticated or unauthorized IP addresses.

You are affected if the SD-WAN Edge firmware version is 4.5.0 or 4.5.1 (falling within >= 4.5.0 to < 4.5.2) AND the management interface is accessible from untrusted networks.

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.

dbcve · scoped
Upgrade available Upgrade to 4.5.2 or later
Fixed in 4.5.2
Interim mitigation

Apply the vendor-supplied security patch for VMware SD-WAN. As an interim measure, restrict network access to the SD-WAN Management interface to trusted networks only and monitor for unauthorized access attempts.

Recommended fix High confidence

VMware SD-WAN Edge firmware 4.5.2 or later

  1. Verify current SD-WAN Edge firmware version by accessing the VMware SD-WAN Orchestrator or Edge device management interface
  2. Download the VMware SD-WAN Edge firmware version 4.5.2 or later from VMware's official download portal
  3. Plan the upgrade during a maintenance window to minimize disruption
  4. Upload the new firmware through the SD-WAN Orchestrator or Edge management interface
  5. Follow VMware's standard firmware upgrade procedure for SD-WAN Edge devices
  6. After upgrade, verify the diagnostic bundle download functionality works correctly and that authentication is now required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sd Wan Edge Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20899 — 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-2023-20899 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