Workplace DesktopApplication · Zoom

CVE-2024-42438

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 5.17.14 / 6.0.11 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
Buffer overflow in some Zoom Workplace Apps, SDKs, Rooms Clients, and Rooms Controllers 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 buffer overflow vulnerability in Zoom Workplace Apps, SDKs, Rooms Clients, and Rooms Controllers allows an authenticated user with network access to trigger the overflow, potentially causing a denial of service condition.

MitigationApply vendor-supplied patches or update all affected Zoom products to the latest fixed versions. Prioritize systems with direct network exposure.

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:< 6.1.0
Meeting Software Development KitApplication
Affected:< 6.1.0
RoomsApplication
Affected:< 6.1.0
Rooms ControllerApplication
Affected:< 6.1.0
WorkplaceApplication
Affected:< 6.1.0
Workplace Virtual Desktop InfrastructureApplication
Affected:< 5.17.14>= 6.0, < 6.0.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 product
    Check Programs and Features (Windows) or Applications folder (Mac) for Zoom Workplace, Zoom Rooms, Zoom Meeting SDK, or Zoom Rooms Controller. Look for the Zoom executable in the installation directory and note the product name.
    Affected if Any Zoom product from the affected list is installed (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI)
  2. Find installed Zoom version
    For desktop apps: Open Zoom client, click Help > About Zoom to display the version number. For Rooms: Access Zoom Rooms controller or web portal, navigate to Account Management or Room Settings to view version. For SDK: Check the SDK version in project references or documentation.
    Affected if A version number is displayed that can be compared to the affected ranges
  3. Compare version to affected ranges
    Match your installed version number against the following vulnerable ranges: Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace: versions below 6.1.0 are vulnerable. Workplace VDI: versions below 5.17.14 OR versions 6.0.0 through 6.0.10 are vulnerable.
    Affected if Installed version is below 6.1.0 (for non-VDI products) OR below 5.17.14 OR between 6.0.0 and 6.0.10 (for VDI)
  4. Confirm network exposure
    Verify if the Zoom client or service has network connectivity enabled. Check if the system can connect to zoom.us or if local network ports used by Zoom (typically 80/443, 8801/8802 for video) are accessible.
    Affected if Network access to Zoom services is enabled, as the attacker requires network access to trigger the overflow

You are affected if any Zoom product from the affected list is installed with a version below 6.1.0 (or the specific VDI ranges) and the system has network exposure.

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.17.14 / 6.0.11 / 6.1.0 or later
Fixed in 5.17.146.0.116.1.0
Interim mitigation

Apply vendor-supplied patches or update all affected Zoom products to the latest fixed versions. Prioritize systems with direct network exposure.

Recommended fix High confidence

6.1.0 (or later) for Workplace Desktop/SDK/Rooms/Room Controller/Workspace; 6.0.11 or 5.17.14 for Workplace VDI

  1. 1. Identify the affected Zoom product and current version installed (Help > About in desktop apps)
  2. 2. For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, and Workplace: Upgrade to version 6.1.0 or later
  3. 3. For Workplace Virtual Desktop Infrastructure: If running 6.0.x, upgrade to 6.0.11 or later; if running 5.x, upgrade to 5.17.14 or later
  4. 4. Download the updated version from the official Zoom download center (zoom.us/download)
  5. 5. Run the installer and follow prompts to complete the upgrade
  6. 6. Verify the new version is installed after upgrade completes
  7. 7. Test that Zoom services start properly and functionality is intact

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
  • 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-42438 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-42438 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