dbcve.org
AccessApplication · VMware

CVE-2022-31700

HIGH · 7.2 CVSS v3.1 Published 2022-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
VMware Workspace ONE Access and Identity Manager contain an authenticated remote code execution vulnerability. VMware has evaluated the severity of this issue to be in the Important severity range with a maximum CVSSv3 base score of 7.2.

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 confidence

VMware Workspace ONE Access and Identity Manager contain an authenticated remote code execution vulnerability where an attacker with valid credentials can execute arbitrary code on the affected system. This is a network-exploitable vulnerability rated 7.2 CVSSv3, indicating significant impact but requiring authentication access.

MitigationApply the vendor-supplied patch or update to VMware Workspace ONE Access and Identity Manager. If immediate patching is not possible, restrict network access to the management interfaces and enforce strict authentication controls.

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
AccessApplication
Affected:= 21.08.0.0= 21.08.0.1
Cloud FoundationApplication
Affected:all versions
Identity ManagerApplication
Affected:= 3.3.6

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed VMware product
    Review installed software or check the product name in the VMware Workspace ONE or Identity Manager console. Common paths: /opt/vmware or check service name 'workspace-one-access' or 'horizon-workspace'.
    Affected if The product is VMware Access, VMware Identity Manager, or VMware Cloud Foundation
  2. Determine the installed version of VMware Access
    Check the version file typically located at /usr/local/horizon/conf/version or via the admin console under System Diagnostics. Alternatively, run: systemctl status workspace-one-access
    Affected if Version is exactly 21.08.0.0 or 21.08.0.1
  3. Determine the installed version of VMware Identity Manager
    Check the version file at /opt/vmware/horizon/workspace/conf/version or query the /etc/vmware/horizon/version file. Can also be viewed in the admin console under About.
    Affected if Version is exactly 3.3.6
  4. Determine if VMware Cloud Foundation is deployed
    Check if the environment uses VMware Cloud Foundation for management. Query the vcf-info or check for Cloud Foundation-specific components: /opt/vmware/vcf/
    Affected if VMware Cloud Foundation is in use (all versions are affected)
  5. Confirm authentication is required for exploitation
    Review access controls and user authentication methods configured for the affected service. This vulnerability requires valid credentials.
    Affected if Valid user accounts exist in the affected VMware product and the version is within the affected ranges

Your environment is affected if you are running VMware Access 21.08.0.0 or 21.08.0.1, VMware Identity Manager 3.3.6, or any version of VMware Cloud Foundation, with valid user accounts configured for authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch or update to VMware Workspace ONE Access and Identity Manager. If immediate patching is not possible, restrict network access to the management interfaces and enforce strict authentication controls.

Recommended fix High confidence

Workspace ONE Access 21.08.0.2+ / Identity Manager 3.3.7+ / Cloud Foundation patched per VMSA-2022-0014

  1. 1. Identify the current version of VMware Workspace ONE Access or Identity Manager installed in your environment.
  2. 2. For Workspace ONE Access: upgrade from version 21.08.0.0 or 21.08.0.1 to version 21.08.0.2 or later.
  3. 3. For Identity Manager: upgrade from version 3.3.6 to version 3.3.7 or later.
  4. 4. For VMware Cloud Foundation: apply the appropriate patch for your specific version as referenced in VMware Security Advisory VMSA-2022-0014.
  5. 5. After upgrading, verify the new version is correctly installed and the vulnerability is resolved.
  6. 6. Test that all critical business workflows function properly post-upgrade.
Caveat Review VMware release notes for any compatibility changes or deprecated features in the new version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-31700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-31700 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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