CVE-2024-24691
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 · uneditedImproper input validation in Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows may allow an unauthenticated user to conduct 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 confidenceImproper input validation in Zoom Desktop Client for Windows, Zoom VDI Client for Windows, and Zoom Meeting SDK for Windows allows an unauthenticated attacker to escalate privileges via network access, achieving code execution with elevated permissions without authentication.
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< 5.16.5< 5.17.0< 5.14.14> 5.14.14, < 5.15.12> 5.15.12, < 5.16.10< 5.16.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zoom product on WindowsCheck for Zoom installation by looking in Add/Remove Programs, or search for Zoom.exe in common locations like C:\Program Files\Zoom or C:\Users\%username%\AppData\Roaming\ZoomAffected if Any Zoom Desktop Client, VDI Client, Meeting SDK, or Zoom Rooms is found on the system
-
Determine the Zoom version numberOpen Zoom, click your profile picture then 'Check for Updates' to see the current version, or right-click Zoom.exe in the installation folder, select Properties, and view the File VersionAffected if Version cannot be determined or is below 5.16.5 for Desktop Client/Meeting SDK, below 5.17.0 for Zoom Rooms, or within the VDI ranges < 5.14.14, 5.14.14-5.15.12, or 5.15.12-5.16.10
-
Verify network exposure of Zoom serviceCheck if Zoom's listening ports (typically 80, 443, 8000-9000 range for Zoom meetings) are exposed to untrusted networks, or if the system is directly internet-facing with Zoom runningAffected if Zoom is running and accessible from untrusted network segments, as the vulnerability requires network access for exploitation
-
Confirm elevated privilege contextCheck if Zoom is running with elevated privileges (Run as Administrator) or if the service runs under a privileged account like LocalSystemAffected if Zoom runs with elevated or system-level privileges, which would allow the attacker to achieve code execution at that higher privilege level
A user is affected if a vulnerable Zoom version (Desktop Client/Meeting SDK < 5.16.5, Zoom Rooms < 5.17.0, or VDI versions in the listed ranges) is installed on Windows with network-accessible Zoom services running at elevated privileges.
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 · scoped5.14.145.15.125.16.5
Organizations must update all Zoom Windows clients to the patched version released by Zoom and inventory all installations to ensure complete coverage.
Upgrade to Zoom 5.16.5+ (Desktop/SDK), Rooms 5.17.0+, or VDI clients to their respective fixed versions (5.14.14/5.15.12/5.16.10 depending on branch)
- Identify which Zoom product is affected: Zoom Desktop Client for Windows, Zoom VDI Client for Windows, Zoom Meeting SDK for Windows, or Zoom Rooms
- For Zoom Desktop Client and Meeting SDK: upgrade to version 5.16.5 or later
- For Zoom Rooms: upgrade to version 5.17.0 or later
- For Zoom VDI Windows Meeting Clients: if previously on <5.14.14, upgrade to 5.14.14 or later; if on 5.14.14-5.15.12, upgrade to 5.15.12 or later; if on 5.15.12-5.16.10, upgrade to 5.16.10 or later
- Verify the installed version after upgrade by checking the application About/Help section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24691 — 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-2024-24691 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