An input validation vulnerability exists in an API component of the orchestrator. An authenticated user can exploit this flaw to manipulate backend queries, which may result in unauthorized access to data beyond their intended privileges and cause the underlying system to initiate unintended outbound network connections.
\nThis issue was discovered internally by Arista and the company is not aware of any malicious uses of this issue in customer networks.
" } ] } ], "references": [ { "url": "https://www.arista.com/en/support/advisories-notices/security-advisory/24365-security-advisory-0145", "name": "Security Advisory 0145", "tags": [ "vendor-advisory" ] } ], "configurations": [ { "lang": "en", "value": "A successful attack requires a valid authenticated session on the VCO portal. The minimum user role required is Enterprise Read Only, the lowest built-in tenant role. No non-default configuration is required.", "supportingMedia": [ { "type": "text/html", "base64": false, "value": "A successful attack requires a valid authenticated session on the VCO portal. The minimum user role required is Enterprise Read Only, the lowest built-in tenant role. No non-default configuration is required.
" } ] } ], "workarounds": [ { "lang": "en", "value": "Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment:\n\n\n\n * Restrict access to the VCO web interface to trusted administrative networks.\n\n * Monitor the VCO for accesses from known malicious source IPs.\n\n * Monitor for unexpected outbound network activity from the VCO host.\n\n * Review recent administrator activity for unexpected changes.", "supportingMedia": [ { "type": "text/html", "base64": false, "value": "Until the fixed software is deployed, operators should apply defense-in-depth controls appropriate for their environment:
\nThe recommended resolution is to upgrade to a fixed VCO release at your earliest convenience.
\nThese vulnerabilities have been fixed in the following releases:
\n