dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2024-24696

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 5.15.15 / 5.16.12 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Improper input validation in Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows may allow an authenticated user to conduct a disclosure of information 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

Improper input validation in Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows allows an authenticated user with low privileges to potentially disclose sensitive information via network access due to insufficient validation of input data.

MitigationApply the latest security update for Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows to address the input validation 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.17.0
Vdi Windows Meeting ClientsApplication
Affected:< 5.15.15> 5.15.15, < 5.16.12> 5.16.12, < 5.17.0
ZoomApplication
Affected:< 5.17.0

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

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

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

  1. Identify Zoom installation on Windows
    Open Programs and Features (appwiz.cpl) or check for Zoom.exe in common installation paths such as C:\Users\%USERNAME%\AppData\Roaming\Zoom\bin\ or C:\Program Files\Zoom\bin\
    Affected if Zoom Desktop Client, VDI Client, or Meeting SDK for Windows is installed
  2. Check Zoom Desktop Client version
    If Zoom is running, click your profile picture or initials, then click 'Check for Updates' or 'About Zoom' to view the version number. Alternatively, right-click Zoom.exe in the installation folder, select Properties, and check the Details tab for the Product Version
    Affected if The installed version is less than 5.17.0
  3. Check Zoom VDI Client version
    For VDI deployments, check the installed VDI client version through your VDI administrator console or by right-clicking the ZoomVDI.exe file in the installation directory, selecting Properties, and viewing the Product Version in the Details tab
    Affected if The installed version is less than 5.15.15, or is between 5.15.16 and 5.16.12 inclusive, or is between 5.16.13 and 5.16.x (where x < 12) or less than 5.17.0
  4. Check Zoom Meeting SDK version
    For developers using the Meeting SDK, check the version listed in your project's dependencies or the installed SDK assembly/dll version by right-clicking the ZoomSDK.dll file, selecting Properties, and viewing the Product Version in the Details tab
    Affected if The installed SDK version is less than 5.17.0
  5. Verify network-facing exposure
    Confirm the Zoom client is configured to connect to meetings or has network connectivity enabled, as the vulnerability is exploitable via network access
    Affected if The Zoom client can receive network connections or is used to join remote meetings

A user is affected if they have any version of Zoom Desktop Client, VDI Client, or Meeting SDK for Windows installed that is earlier than version 5.17.0 and the client has network connectivity enabled.

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.15 / 5.16.12 / 5.17.0 or later
Fixed in 5.15.155.16.125.17.0
Interim mitigation

Apply the latest security update for Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows to address the input validation vulnerability.

Recommended fix High confidence

Version 5.17.0 or later for all affected Zoom products (Desktop Client, VDI Client, Meeting SDK)

  1. Identify the affected Zoom product in use: Zoom Desktop Client for Windows, Zoom VDI Client for Windows, or Zoom Meeting SDK for Windows
  2. Navigate to the official Zoom download page at www.zoom.com
  3. Download Zoom version 5.17.0 or later for the applicable product
  4. Install the updated Zoom client or SDK
  5. Verify the installed version matches or exceeds 5.17.0

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-2024-24696 — 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-2024-24696 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