Virtual Desktop InfrastructureApplication · Zoom

CVE-2023-39213

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 5.15.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper neutralization of special elements in Zoom Desktop Client for Windows and Zoom VDI Client before 5.15.2 may allow an unauthenticated user to enable an escalation of privilege via network access.

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

This is an injection-type vulnerability (improper neutralization of special elements) in Zoom's Windows Desktop Client and VDI Client versions prior to 5.15.2. An unauthenticated attacker with network access can exploit this to achieve privilege escalation, likely through malicious input being processed without proper sanitization.

MitigationUpgrade Zoom Desktop Client for Windows and Zoom VDI Client to version 5.15.2 or later to remediate this vulnerability.

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
Virtual Desktop InfrastructureApplication
Affected:< 5.15.2
ZoomApplication
Affected:< 5.15.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Zoom client version on Windows
    Open Zoom, click your profile picture or initials in the top-right, then click 'Check for Updates' or go to Help > About Zoom to view the version number
    Affected if The displayed version is earlier than 5.15.2 (for example, 5.14.x, 5.13.x, or any version number below 5.15.2)
  2. Verify Windows Desktop Client is in use
    Confirm the installed client is the standard Zoom Desktop Client for Windows or the Zoom VDI Client, as this vulnerability only affects Windows versions
    Affected if The client is Zoom for Windows Desktop or VDI Client rather than macOS, Linux, or mobile platforms
  3. Check Zoom process is active or installed
    Open Task Manager or use 'Get-Process Zoom*' in PowerShell to see if Zoom is currently running, or check Program Files for Zoom installation
    Affected if Zoom is installed and running on the Windows system with an affected version
  4. Confirm network exposure
    Determine if the Windows machine with Zoom installed is accessible over the network, as the attacker requires network access to exploit this flaw
    Affected if The Zoom client system is network-accessible to unauthenticated attackers

You are affected if you have Zoom Desktop Client or VDI Client for Windows running version 5.15.2 or earlier.

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
Upgrade available Upgrade to 5.15.2 or later
Fixed in 5.15.2
Interim mitigation

Upgrade Zoom Desktop Client for Windows and Zoom VDI Client to version 5.15.2 or later to remediate this vulnerability.

Recommended fix High confidence

5.15.2

  1. Close all running Zoom Desktop Client or Zoom VDI Client instances
  2. Navigate to the official Zoom download page at zoom.us/download or your organization's software distribution center
  3. Download Zoom Desktop Client for Windows version 5.15.2 or later
  4. Run the Zoom installer and complete the upgrade process
  5. Verify the installed version by launching Zoom and checking Help > About Zoom to confirm version 5.15.2 or higher is installed

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

Fix this in Virtual Desktop Infrastructure Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39213 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39213 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