dbcve.org
Workplace DesktopApplication · Zoom

CVE-2024-27239

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-25
Fix available
A fix is available. Upgrade to 5.15.17 / 5.16.15 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
Use after free in some Zoom Workplace Apps and SDKs may allow an authenticated user to conduct a denial of service 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

A Use After Free (UAF) vulnerability in Zoom Workplace Apps and SDKs allows an authenticated attacker to cause denial of service via network access. The vulnerability stems from improper memory management where memory is accessed after being freed, leading to application crash or unpredictable behavior.

MitigationUpdate Zoom Workplace Apps and SDKs to the latest patched versions provided by Zoom. Ensure all deployments are running authenticated, patched versions to prevent exploitation.

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
Workplace DesktopApplication
Affected:< 5.17.11
Meeting Software Development KitApplication
Affected:< 5.17.11
RoomsApplication
Affected:< 6.0.0
WorkplaceApplication
Affected:< 5.17.11
Workplace Virtual Desktop InfrastructureApplication
Affected:< 5.15.17>= 5.16.0, < 5.16.15>= 5.16.16, < 5.17.11

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify installed Zoom products
    Check for Zoom executables in common installation directories (C:\Program Files\Zoom, C:\Program Files (x86)\Zoom, or ~/.zoom) or run 'where zoom.exe' on Windows, 'which zoom' on Linux/Mac
    Affected if No Zoom products are found on the system, so the CVE does not apply
  2. Determine Zoom Workplace Desktop version
    Open Zoom Desktop app, click profile picture or help menu, select 'About Zoom' to view version number, or run 'Zoom.exe --version' from the installation directory
    Affected if Version is below 5.17.11
  3. Determine Zoom Meeting SDK version
    Check the SDK version file or library manifest in the installed SDK directory, or query the SDK version via its version API if integrated into a custom application
    Affected if Version is below 5.17.11
  4. Determine Zoom Rooms version
    Open Zoom Rooms controller interface and navigate to the about or settings section to view the version, or check the ZoomRooms service version
    Affected if Version is below 6.0.0
  5. Determine Zoom Workplace VDI version
    Check the VDI client version through the VDI environment's about or version dialog, or query the VDI agent version through the virtual desktop infrastructure
    Affected if Version falls into any of these ranges: below 5.15.17, OR 5.16.0 to below 5.16.15, OR 5.16.16 to below 5.17.11

If any installed Zoom product matches an affected version range listed above, the environment is potentially affected by this UAF 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 5.15.17 / 5.16.15 / 5.17.11 or later
Fixed in 5.15.175.16.155.17.11
Interim mitigation

Update Zoom Workplace Apps and SDKs to the latest patched versions provided by Zoom. Ensure all deployments are running authenticated, patched versions to prevent exploitation.

Recommended fix High confidence

5.17.11 (or 6.0.0 for Rooms; 5.15.17/5.16.15/5.17.11 for VDI depending on branch)

  1. 1. Identify the affected Zoom product and current version installed (Workplace Desktop, Meeting SDK, Rooms, Workplace, or Workplace VDI)
  2. 2. For Workplace Desktop, Meeting SDK, or Workplace: Upgrade to version 5.17.11 or later
  3. 3. For Rooms: Upgrade to version 6.0.0 or later
  4. 4. For Workplace VDI: If running 5.15.x, upgrade to 5.15.17 or later; if running 5.16.x, upgrade to 5.16.15 or later; if running 5.17.x, upgrade to 5.17.11 or later
  5. 5. Verify the upgrade was successful by checking the application version
  6. 6. Test that Zoom functionality remains operational after the update

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

Fix this in Workplace Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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