CVE-2023-20886
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 contains an open redirect vulnerability. A malicious actor may be able to redirect a victim to an attacker and retrieve their SAML response to login as the victim user.
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 has an open redirect vulnerability where the console can be manipulated to redirect users to attacker-controlled URLs. An attacker can craft a malicious link that passes through the UEM console and redirects the victim to the attacker's site, where the SAML authentication response can be intercepted. This allows the attacker to capture the victim's SAML response and subsequently authenticate as the victim user.
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>= 22.3.0.2, < 22.3.0.48>= 22.6.0.1, < 22.6.0.36>= 22.9.0.1, < 22.9.0.29>= 22.12.0.1, < 22.12.0.20>= 23.2.0.1, < 23.2.0.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate the Workspace ONE UEM console versionLog in to the UEM admin console and navigate to System > Settings > General > About, or check the console footer for the version numberAffected if The displayed version matches one of the affected ranges: 22.3.0.2 to 22.3.0.47, 22.6.0.1 to 22.6.0.35, 22.9.0.1 to 22.9.0.28, 22.12.0.1 to 22.12.0.19, or 23.2.0.1 to 23.2.0.9
-
Confirm SAML-based authentication is configuredIn the UEM console, go to Groups & Settings > All Settings > System > Enterprise Integration > SSO (Single Sign-On) and verify if SAML authentication is enabledAffected if SAML authentication is enabled and the console version is within the affected ranges listed above
-
Verify redirect URL validation is not enforcedCheck the SSO settings for any URL validation, allow-listing, or redirect destination restrictions under the SAML configuration sectionAffected if No URL allow-listing or redirect destination validation is configured and the console version is vulnerable
-
Inspect URL parameters during SAML login flowAccess the UEM login page and examine whether the 'redirect' or 'RelayState' parameter can be modified to an external domain without being blockedAffected if External URLs are accepted as redirect destinations without validation or warning
You are affected if your UEM console version falls within any of the listed affected ranges AND SAML authentication is configured, since the open redirect allows manipulation of the SAML authentication flow to external attacker-controlled URLs.
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 · scoped22.3.0.4822.6.0.3622.9.0.29
Apply the VMware security patch for CVE-2023-20886 to the Workspace ONE UEM console. As a compensating control, implement URL validation and allow-listing for redirect destinations, and monitor for suspicious redirect patterns in authentication flows.
22.3.0.48+ / 22.6.0.36+ / 22.9.0.29+ / 22.12.0.20+ (depending on your branch)
- 1. Identify the current installed version of Workspace ONE UEM from the console or admin interface
- 2. Determine which version branch your current installation falls into (22.3.x, 22.6.x, 22.9.x, or 22.12.x)
- 3. For branch 22.3.x: upgrade to version 22.3.0.48 or later
- 4. For branch 22.6.x: upgrade to version 22.6.0.36 or later
- 5. For branch 22.9.x: upgrade to version 22.9.0.29 or later
- 6. For branch 22.12.x: upgrade to version 22.12.0.20 or later
- 7. After upgrade, verify the console is accessible and functioning normally
- 8. Test that SAML authentication flows work correctly and no redirects occur to untrusted domains
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20886 — 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-2023-20886 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