CVE-2018-6961
VMware SD-WAN Edge by VeloCloud Command Injection Vulnerability
VMware SD-WAN Edge
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.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 25 March 2022. US federal agencies were required to remediate it by 15 April 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 85.5%, which is higher than 99.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2018-6961 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2018-6961.
What does CVE-2018-6961 affect?
CVE-2018-6961 affects VMware SD-WAN Edge. 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.
How severe is CVE-2018-6961?
CVE-2018-6961 is rated HIGH with a CVSS base score of 8.1. EPSS puts the probability of exploitation in the next 30 days at 85.5%, higher than 99.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 April 2022.
How should organisations respond to CVE-2018-6961?
Apply the vendor patch for VMware SD-WAN Edge as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.