dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2023-49647

HIGH · 7.8 CVSS v3.1 Published 2024-01-12
Fix available
A fix is available. Upgrade to 5.14.14 / 5.15.12 or later.
See remediation →
80/100
Remediation priority · High
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 access control in Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom SDKs for Windows before version 5.16.10 may allow an authenticated user to conduct an escalation of privilege via local 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

Improper access control in Zoom Desktop Client for Windows, VDI Client for Windows, and Zoom SDKs for Windows before version 5.16.10 allows an authenticated local user to escalate privileges. This is a client-side vulnerability requiring local access to the Windows system where Zoom is installed.

MitigationUpdate Zoom Desktop Client for Windows, VDI Client, and SDKs to version 5.16.10 or later to remediate the improper access control 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
Meeting Software Development KitApplication
Affected:< 5.16.10
Video Software Development KitApplication
Affected:< 5.16.10
ZoomApplication
Affected:< 5.16.10
Virtual Desktop InfrastructureApplication
Affected:< 5.14.14>= 5.15.0, < 5.15.12>= 5.16.0, < 5.16.10

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Locate Zoom installation directory
    Check for Zoom.exe in common installation paths: C:\Program Files\Zoom\bin\ or C:\Program Files (x86)\Zoom\bin\. You can also use PowerShell: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Recurse -Filter 'Zoom.exe' -ErrorAction SilentlyContinue
    Affected if Zoom.exe is found on the system
  2. Determine installed Zoom version
    Right-click on Zoom.exe, select Properties, then look at the Details tab for Product Version. Alternatively, run: (Get-Item 'C:\Program Files\Zoom\bin\Zoom.exe').VersionInfo.FileVersion
    Affected if Version displayed is below 5.16.10 (or for VDI: below 5.14.14, between 5.15.0-5.15.11, or between 5.16.0-5.16.9)
  3. Check Windows Registry for installed Zoom products
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\. Look for keys with 'Zoom' in the DisplayName. Check the DisplayVersion value.
    Affected if A Zoom product entry shows a version below 5.16.10 (or VDI versions in the affected ranges)
  4. Identify if Zoom VDI Client is installed
    Check for VDI-specific components in C:\Program Files\Zoom\VDI\ or look for 'Zoom VDI' in Add/Remove Programs. Query registry: Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Zoom*VDI*'}
    Affected if Zoom VDI is installed with version below 5.14.14, or between 5.15.0-5.15.11, or between 5.16.0-5.16.9
  5. Check for Zoom SDK installations
    Search development machine directories where Zoom SDKs may be installed, such as C:\ZoomSDK\ or within project folders. Look for ZoomSDK.dll or version metadata files. Query: Get-ChildItem -Path 'C:\' -Recurse -Filter '*Zoom*SDK*.dll' -ErrorAction SilentlyContinue | Select-Object -First 10 FullName
    Affected if Zoom Meeting SDK or Video SDK DLLs are found with version information indicating a build below 5.16.10

The system is affected if any Zoom product (Desktop Client, VDI, or SDK) for Windows is installed with a version below 5.16.10 (or the specific VDI ranges listed), and the attacker has local authenticated access to that Windows machine.

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.14.14 / 5.15.12 / 5.16.10 or later
Fixed in 5.14.145.15.125.16.10
Interim mitigation

Update Zoom Desktop Client for Windows, VDI Client, and SDKs to version 5.16.10 or later to remediate the improper access control vulnerability.

Recommended fix High confidence

5.16.10 (Meeting SDK, Video SDK, Zoom Desktop Client); 5.14.14, 5.15.12, or 5.16.10+ for VDI depending on current version

  1. 1. Identify which Zoom product(s) are installed: Meeting SDK, Video SDK, Zoom Desktop Client, or VDI Client for Windows
  2. 2. For Zoom Desktop Client: Open the application, go to Help > About Zoom to check the current version
  3. 3. Download the latest version of Zoom Desktop Client for Windows from the official Zoom website (zoom.us)
  4. 4. For Zoom SDKs: Update the SDK package in your application to version 5.16.10 or later via your package manager or by downloading from Zoom's developer portal
  5. 5. For Zoom VDI: Contact your VDI administrator to ensure the VDI client is updated to version 5.14.14, 5.15.12, or 5.16.10 or later based on your current version branch
  6. 6. After updating, restart the Zoom application or reconnect the VDI session
  7. 7. Verify the installed version meets the minimum requirement: 5.16.10 or later for Meeting SDK/Video SDK/Zoom; or 5.14.14+/5.15.12+/5.16.10+ for VDI

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

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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