VeloCloud Orchestrator (VCO) on-prem has a security issue where this issue may allow a remote attacker to access privileged internal functionality and impact the VCO host. Successful exploitation may compromise the confidentiality, integrity, and availability of the orchestrator and data managed by the orchestrator.
Hosted, including Dedicated, versions of VCO were impacted and have already been patched.
VCO is exposed if certificate based authentication from the VeloCloud Edge to VeloCloud Orchestrator (VCO) is configured. Access to the public portion of the VeloCloud Edge authentication certificate is required. A successful attack requires network access to the VCO web interface. VCO tenant or operator credentials are not required for this exposure.
Deployments that restrict VCO web interface access to trusted administrative networks can reduce risk of exposure.
Until fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment:
- Restrict access to the VCO web interface to trusted administrative networks.
- Monitor the VCO for accesses from known malicious source IPs.
- Monitor for unexpected outbound network activity from the VCO host.
- Consider blocking outbound ports not needed for normal activities.
- Monitor for backdoor daemons and webshells.
- Review recent administrator activity for unexpected changes.
The recommended resolution is to upgrade to a remediated VCO software version at your earliest convenience. These vulnerabilities have been fixed in the following releases:
- VCO 5.2.3.16 and later in the 5.2.3 train
- VCO 6.4.2.8 and later in the 6.4.2 train
Releases in other release trains that fix this will be added over time. For VCOs not on a supported release train, customers can contact TAC to discuss possible upgrade options.