Workspace One Uem ConsoleApplication · VMware
CVE-2021-22054
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 UEM console 20.0.8 prior to 20.0.8.37, 20.11.0 prior to 20.11.0.40, 21.2.0 prior to 21.2.0.27, and 21.5.0 prior to 21.5.0.37 contain an SSRF vulnerability. This issue may allow a malicious actor with network access to UEM to send their requests without authentication and to gain access to sensitive information.
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 · high confidenceVMware Workspace ONE UEM console contains a Server-Side Request Forgery (SSRF) vulnerability allowing unauthenticated attackers with network access to send arbitrary requests through the vulnerable server. This can enable internal network reconnaissance and access to sensitive information that the UEM server can reach. The vulnerability affects multiple version branches (20.0.8, 20.11.0, 21.2.0, and 21.5.0) prior to their respective patched releases.
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
Workspace One Uem ConsoleApplication
>= 20.0.8.0, < 20.0.8.36>= 20.11.0.0, < 20.11.0.40>= 21.2.0.0, < 21.2.0.27>= 21.5.0.0, < 21.5.0.37CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 if VMware Workspace ONE UEM console is presentCheck if the UEM console service is running on your system or if the web interface is accessible on typical ports (typically 443 or 8443). Look for processes named 'Workspace ONE' or 'UEM' in running services.Affected if The product is installed and running on the system
-
Determine the installed UEM console versionLog into the Workspace ONE UEM console admin interface and navigate to System Settings > Enterprise Integration > Console Settings, or check version information in the console's about/help page. Alternatively, check installation directories for version manifest files.Affected if The version number cannot be determined or is not visible in the console
-
Compare your version against affected rangesCheck if your installed version falls into any of these ranges: 20.0.8.0 through 20.0.8.35, 20.11.0.0 through 20.11.0.39, 21.2.0.0 through 21.2.0.26, or 21.5.0.0 through 21.5.0.36Affected if Your installed version is within any of the four affected version ranges listed
-
Verify network accessibility of the consoleDetermine if the UEM console is exposed to network access from untrusted sources. Check firewall rules, load balancer configurations, or VPN settings that control access to the console's URL. The vulnerability requires network access to the console by unauthenticated attackers.Affected if The console is reachable from untrusted or external networks without proper access controls
You are affected if the UEM console is running a version between 20.0.8.0-20.0.8.35, 20.11.0.0-20.11.0.39, 21.2.0.0-21.2.0.26, or 21.5.0.0-21.5.0.36 and is accessible over the network to unauthenticated attackers.
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 · scoped20.0.8.3620.11.0.4021.2.0.27
Apply the vendor-provided patches (20.0.8.37, 20.11.0.40, 21.2.0.27, or 21.5.0.37 or later) to all affected UEM console installations. Network segmentation and restricting the UEM console's network exposure can provide additional defense-in-depth until patching is completed.
20.0.8.37, 20.11.0.40, 21.2.0.27, or 21.5.0.37 (select the appropriate version based on your release branch)
- 1. Identify the current version of Workspace ONE UEM Console by accessing the console dashboard or system information
- 2. Determine which version branch you are on (20.0.8.x, 20.11.0.x, 21.2.0.x, or 21.5.0.x)
- 3. Review the VMware Workspace ONE UEM upgrade documentation for your specific version path
- 4. Create a complete backup of the current Workspace ONE UEM environment and database
- 5. Schedule a maintenance window for the upgrade
- 6. Download the appropriate fixed version from VMware (20.0.8.37 or later for 20.0.8 branch, 20.11.0.40 or later for 20.11.0 branch, 21.2.0.27 or later for 21.2.0 branch, or 21.5.0.37 or later for 21.5.0 branch)
- 7. Follow VMware's documented upgrade procedure to apply the update
- 8. After upgrade, verify the console is functioning properly and review audit logs to confirm no unauthorized SSRF attempts occurred
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Workspace One Uem Console
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22054 — 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-2021-22054 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