CVE-2024-24697
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 · uneditedUntrusted search path in some Zoom 32 bit Windows clients 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 · high confidenceUntrusted search path vulnerability in Zoom 32-bit Windows clients allows an authenticated local user to perform privilege escalation through DLL hijacking. The client loads executable code from locations that can be controlled by the user, enabling elevation from standard user to higher privileges.
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.17.0< 5.17.0< 5.15.5> 5.15.5, < 5.16.2> 5.16.2, < 5.17.5< 5.17.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if 32-bit Zoom client is installedOn Windows, open Programs and Features or run 'Get-ItemProperty' on the Zoom installation directory. Look for Zoom's executable (zoom.exe) in Program Files (x86) which indicates a 32-bit installation.Affected if The 32-bit version of Zoom is installed on the system
-
Determine installed Zoom versionRight-click on the Zoom application in Programs and Features and select Properties, or run 'zoom.exe /ver' in the Zoom installation folder to retrieve the version number.Affected if The version number returned is lower than 5.17.0 (or falls within the specific VDI ranges: < 5.15.5, 5.15.5-5.16.2, or 5.16.2-5.17.5)
-
Verify Zoom process is runningOpen Task Manager and check if zoom.exe is currently active, or run 'Get-Process zoom' in PowerShell to list running Zoom processes.Affected if The Zoom client process is running under a standard user account while an attacker could place malicious DLLs in a writeable location in the DLL search path
A user is affected if they have a 32-bit Windows Zoom client installed with a version below 5.17.0 (or within the VDI-specific affected ranges) and the client is or can be run by standard users.
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.15.55.16.25.17.0
Apply Zoom's security patch by updating to the latest client version; as defense-in-depth, implement application whitelisting and restrict write access to directories in the DLL search path.
5.17.0 (or 5.17.5 for VDI Windows Meeting Clients)
- Identify which Zoom product component is affected (Meeting Software Development Kit, Rooms, VDI Windows Meeting Clients, or Zoom client)
- For Meeting Software Development Kit: upgrade to version 5.17.0 or later
- For Rooms: upgrade to version 5.17.0 or later
- For VDI Windows Meeting Clients: upgrade to version 5.17.5 or later
- For Zoom client: upgrade to version 5.17.0 or later
- Verify the installation of the updated version and restart the application if needed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24697 — 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-24697 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