Arista Networks VeloCloud Orchestrator (VCO) On-Prem
Security Advisory 0183
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5.2.0, <= 5.2.3.15
- >= 6.1.0, <= 6.1.3.7
- >= 6.4.0, <= 6.4.2.7
- >= 7.0.0, <= 7.0.0.2
Mitigation
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.
Workaround
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.
References
- Vendor advisory arista.com/en/support/advisories-notices/secur…
Timeline
Days relative to CVE publicationNo public PoC found yet; added to CISA KEV 0 h after publication.
PoC repositories
Found on GitHub.No PoC repositories found yet.