Severity: CRITICAL · Priority: P1 — active exploitation of a maximum-severity SD-WAN control-plane flaw, escalate on hit
These rules detect attempted exploitation of a maximum-severity flaw in Arista's VeloCloud Orchestrator, the server that manages and controls all Edge devices in a VeloCloud SD-WAN deployment. The flaw lets an unauthenticated attacker access internal privileged functions and take over the orchestrator host with no credentials. The risk extends well beyond the orchestrator itself: a compromised VCO may also give attackers access to all the SD-WAN Edge devices it manages, potentially turning the control plane into a pivot point into the entire network it governs. The flaw only affects on-premises VCO deployments where certificate-based authentication between Edges and the orchestrator is configured.
The exploitation rule watches for the specific request indicator used to access privileged VCO functions without authentication. The implant C2 rule watches for a compromised VCO reaching back to attacker infrastructure — a hit there suggests the orchestrator has already been compromised and a persistent implant is active.
A hit on the exploitation rule indicates an active attempt against one of your VCO servers. Confirm whether the targeted VCO uses certificate-based Edge authentication; if so, assume the attempt may have succeeded and escalate to incident response immediately. Because there is no single definitive indicator of compromise for this flaw, do not treat absence of further detections as proof the VCO is clean — review web access logs for unusual URL paths, encoded characters, or high request rates from unexpected sources, and isolate the VCO from the broader network while investigating. A compromised VCO may have already pivoted to Edge devices, so assess those as well. Upgrade to a fixed release as the definitive remediation: 5.2 and 6.4 branches have fixes as of September 22, 2026; if your VCO is on 6.1 or 7.0, follow Arista's interim guidance and contact their support.