CVE-2020-4006
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVMware Workspace One Access, Access Connector, Identity Manager, and Identity Manager Connector address have a command injection vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCommand injection vulnerability in VMware Workspace One Access, Access Connector, Identity Manager, and Identity Manager Connector allowing execution of arbitrary commands on the affected systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.3.1= 3.3.2= 3.3.3= 3.3.1= 3.3.2= 3.3.3= 20.01= 20.10= 4.0= 4.0.1>= 8.0, <= 8.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed VMware identity productCheck installed software or running services for VMware Identity Manager, Workspace One Access, or related components. Look for service names like 'vmware-identity-manager', 'horizon-workspace', or similar.Affected if The product matches one of: VMware Identity Manager, VMware Identity Manager Connector, VMware Workspace One Access, VMware Cloud Foundation, or VMware vRealize Suite Lifecycle Manager
-
Check product version numberUse the product's administrative console, service management interface, or check installed package/version information. For Identity Manager, typically found in /opt/vmware/horizon/workspace/ or via the admin UI at /SAAS/admin. For Cloud Foundation and vRealize LCM, check the VMware product UI or API.Affected if Version equals 3.3.1, 3.3.2, or 3.3.3 (Identity Manager/Connector); equals 20.01 or 20.10 (Workspace One Access); equals 4.0 or 4.0.1 (Cloud Foundation); or is between 8.0 and 8.2 inclusive (vRealize Suite Lifecycle Manager)
-
Verify administrative interface is accessibleConfirm the administrative web interface (typically port 443/https) is reachable. The vulnerability is exploitable through the configurator or admin endpoints. Check network exposure and firewall rules.Affected if The administrative interface is exposed to network traffic, particularly untrusted networks
-
Check for evidence of compromiseReview system logs, particularly authentication and command execution logs, for unexpected commands, shells spawned, or suspicious admin actions around the configurator endpoint.Affected if Unexpected commands appear in logs, especially those originating from admin API endpoints
Your environment is affected if any of these VMware products are running the specific versions listed and the administrative interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply vendor-supplied patches or updates for affected VMware products; restrict network access to administrative interfaces.
Identity Manager/Connector: 3.3.4+ | One Access: 20.02 or 20.10.0.1+ | Cloud Foundation: 4.0.2+ | vRSLCM: 8.3+
- 1. Identify the exact VMware product and version running in your environment from: Identity Manager (3.3.1-3.3.3), Identity Manager Connector (3.3.1-3.3.3), One Access (20.01, 20.10), Cloud Foundation (4.0, 4.0.1), or Vrealize Suite Lifecycle Manager (8.0-8.2)
- 2. For Identity Manager 3.3.x: upgrade to version 3.3.4 or later
- 3. For Identity Manager Connector 3.3.x: upgrade to version 3.3.4 or later
- 4. For One Access 20.01: apply patch OR upgrade to 20.02 or later
- 5. For One Access 20.10: apply patch OR upgrade to 20.10.0.1 or later
- 6. For Cloud Foundation 4.0/4.0.1: upgrade to 4.0.2 or later
- 7. For Vrealize Suite Lifecycle Manager 8.0-8.2: upgrade to 8.3 or later
- 8. After upgrade, verify the OAuth2 ACS endpoint is no longer exposed to unauthenticated network access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-4006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data