dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Nsx Sd Wan By VelocloudApplication · VMware

CVE-2018-6961

HIGH · 8.1 CVSS v3.1 Published 2018-06-11
Fix available
A fix is available. Upgrade to 3.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit 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 NSX SD-WAN Edge by VeloCloud prior to version 3.1.0 contains a command injection vulnerability in the local web UI component. This component is disabled by default and should not be enabled on untrusted networks. VeloCloud by VMware will be removing this service from the product in future releases. Successful exploitation of this issue could result in remote code execution.

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 confidence

VMware NSX SD-WAN Edge by VeloCloud prior to version 3.1.0 contains a command injection vulnerability in the local web UI component. An unauthenticated attacker can inject arbitrary commands through this web interface, potentially achieving remote code execution on the affected device.

MitigationUpgrade to VMware NSX SD-WAN Edge version 3.1.0 or later. Ensure the local web UI component remains disabled and is not exposed on untrusted networks.

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
Nsx Sd Wan By VelocloudApplication
Affected:< 3.1.0

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Identify NSX SD-WAN Edge installation
    Locate the VMware NSX SD-WAN Edge (VeloCloud) service on the system. Check for processes named 'velocity' or 'vcg', or look for the software in /opt/velocloud or similar installation directories.
    Affected if The software is not installed or the installation path cannot be located.
  2. Determine installed version
    Run the command to retrieve the Edge version, typically 'vcg-cli --version' or check theabout page in the web UI if accessible. Compare the version number against the 3.1.0 threshold.
    Affected if The installed version is anything less than 3.1.0.
  3. Verify web UI component status
    Check if the local web UI service is running and enabled. This may involve querying the service status via 'systemctl status velocloud-ui' or similar, or by inspecting configuration files in the installation directory for web UI enablement flags.
    Affected if The local web UI component is currently enabled and running.
  4. Assess network exposure of web UI
    Determine if the web UI is bound to any network interface other than localhost. Check the service listening addresses using 'netstat -tlnp | grep -E "(vcg|velocity|ui)"' or review firewall rules that may allow external access to ports 443 or 8443.
    Affected if The web UI is accessible from network interfaces other than localhost, particularly from untrusted networks.

You are affected if VMware NSX SD-WAN Edge version is below 3.1.0 AND the local web UI component is enabled and network-accessible.

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 3.1.0 or later
Fixed in 3.1.0
Interim mitigation

Upgrade to VMware NSX SD-WAN Edge version 3.1.0 or later. Ensure the local web UI component remains disabled and is not exposed on untrusted networks.

Recommended fix High confidence

3.1.0

  1. Obtain the VMware NSX SD-WAN Edge version 3.1.0 or later from VMware's official download portal
  2. Review VMware's upgrade documentation for NSX SD-WAN by VeloCloud
  3. Ensure proper backups of current configuration are in place
  4. Execute the upgrade process following VMware's documented procedures
  5. Verify the upgrade was successful and the local web UI component is either disabled or running the patched version
  6. Confirm the version post-upgrade shows 3.1.0 or later
Caveat Review VMware upgrade documentation for any specific prerequisites or migration considerations; the local web UI service is being removed in future releases

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

Fix this in Nsx Sd Wan By Velocloud Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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