dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2024-27238

MEDIUM · 6.3 CVSS v3.1 Published 2024-07-15
Fix available
A fix is available. Upgrade to 6.0.0 or later.
See remediation →
66/100
Remediation priority · Elevated
No privileges

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
Race condition in the installer for some Zoom Apps and SDKs for Windows before version 6.0.0 may allow an authenticated user to conduct a privilege escalation 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 confidence

A race condition exists in the installer for Zoom Apps and SDKs for Windows versions prior to 6.0.0. This timing vulnerability allows an authenticated local user to exploit a window of opportunity during the installation process to manipulate file system or registry operations, potentially achieving elevated privileges on the affected system.

MitigationUpgrade Zoom Apps and SDKs for Windows to version 6.0.0 or later to obtain the patched installer that resolves the race condition.

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:< 6.0.0
RoomsApplication
Affected:< 6.0.0
Workplace DesktopApplication
Affected:< 6.0.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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 installed Zoom product
    Open Windows Settings > Apps > Installed apps, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Zoom*'}
    Affected if Any Zoom product (Meeting SDK, Rooms, or Workplace Desktop) is listed as installed
  2. Check Zoom Workplace Desktop version
    If Zoom Workplace Desktop is installed, right-click the Zoom icon in the taskbar, click on the user profile picture, and note the version number shown, or check C:\Users\%USERNAME%\AppData\Roaming\Zoom\bin\Zoom.exe properties for version info
    Affected if The displayed version is lower than 6.0.0 (for example, 5.x.x series)
  3. Check Zoom Rooms version
    Open the Zoom Rooms application and navigate to the Account Settings or Room Settings, or check the Zoom Rooms service version via Windows Services snap-in (services.msc) looking for Zoom Rooms service
    Affected if The Zoom Rooms version shown is lower than 6.0.0
  4. Check Zoom Meeting SDK version
    If Zoom Meeting Software Development Kit is installed, locate the SDK installation directory and check the version.properties or version.dll, or check the product version via PowerShell: Get-ItemProperty 'C:\path\to\ZoomSDK\ZoomSDK.exe' | Select-Object VersionInfo
    Affected if The SDK version is below 6.0.0

A user is affected if any Zoom product (Workplace Desktop, Rooms, or Meeting SDK) is installed with a version number lower than 6.0.0, as the installer for those versions contained the race condition vulnerability.

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 6.0.0 or later
Fixed in 6.0.0
Interim mitigation

Upgrade Zoom Apps and SDKs for Windows to version 6.0.0 or later to obtain the patched installer that resolves the race condition.

Recommended fix High confidence

Meeting SDK, Rooms, and Workplace Desktop version 6.0.0

  1. 1. Download the Zoom application installer from the official Zoom website (www.zoom.com)
  2. 2. Ensure you have administrative privileges on the Windows machine
  3. 3. Close all running Zoom applications and processes
  4. 4. Run the installer for Meeting SDK, Rooms, or Workplace Desktop version 6.0.0 or later
  5. 5. Follow the on-screen installation prompts to complete the upgrade
  6. 6. Verify the installed version matches 6.0.0 or higher after installation completes

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

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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