Assessment
Why it matters
EPSS is 1.1%; technical severity is CVSS 8.8.
The VeloCloud Orchestrator does not apply correct input validation which allows for blind SQL-injection. A malicious actor with tenant access to Velocloud Orchestrator could enter specially crafted SQL queries and obtain data to which they are not privileged.
Who should care
- Teams operating VeloCloud Orchestrator
- Vulnerability and exposure management teams
- Security operations teams monitoring exploitation activity
Response plan
What I would do
- Confirm whether VeloCloud Orchestrator is present in the environment.
- Identify affected versions and establish whether vulnerable services are exposed or reachable.
- VMware Security advisory VMSA-2020-0016
- Review relevant security telemetry for evidence of attempted or successful exploitation.
- Document the remediation decision and track it to verified completion.
Treatment intelligence
Remediation intelligence
Vendor sources are listed before government and third-party guidance. Confirm product applicability and change prerequisites before deployment.
Verification noteAutomated link verification has not completed for this guidance yet.
Technical details
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CWE
- CWE-89
- Affected versions
- Arista VeloCloud Orchestrator (Start Including 3.1.1, End Excluding 3.3.2 | Version 3.3.2 | Version 3.4.0)
- Fixed versions
- Arista VeloCloud Orchestrator (Fixed from 3.3.2)
- Published
- 8 July 2020
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
Signal timeline
- CVE published
- Latest EPSS score: 1.1%
- Signal calculated at 14