dbcve.org
Workplace DesktopApplication · Zoom

CVE-2024-27241

HIGH · 7.5 CVSS v3.1 Published 2024-07-15
Fix available
A fix is available. Upgrade to 5.17.13 / 6.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Improper input validation in some Zoom 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

Improper input validation in Zoom Apps and SDKs allows authenticated users to cause denial of service via network access. The vulnerability stems from insufficient validation of input data, which can be exploited to crash the application or make it unresponsive.

MitigationApply patches or updates provided by Zoom for affected Apps and SDK versions. Implement robust input validation and consider rate limiting on network endpoints to mitigate DoS conditions.

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.0.0
Meeting Software Development KitApplication
Affected:< 6.0.0
RoomsApplication
Affected:< 6.0.0
WorkplaceApplication
Affected:< 6.0.0
Workplace Virtual Desktop InfrastructureApplication
Affected:< 5.17.13

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 type
    Determine which Zoom product is in use: Zoom Workplace Desktop client, Zoom Meeting SDK, Zoom Rooms, Zoom Workplace, or Zoom Workplace VDI. Check the application name and purpose in the system or documentation.
    Affected if The product is any of the affected Zoom products listed in the CVE.
  2. Check Zoom Workplace Desktop version
    Open the Zoom desktop client, go to the profile picture or gear icon, select 'Help' then 'About Zoom'. Alternatively, right-click the Zoom.exe file in Program Files and view Properties > Details for the File Version.
    Affected if The installed version is below 6.0.0 (any version from 5.x.x and earlier).
  3. Check Zoom Rooms version
    Open the Zoom Rooms controller interface or log into the Zoom web portal and navigate to Zoom Rooms management to view the installed version number.
    Affected if The installed version is below 6.0.0.
  4. Check Zoom Meeting SDK version
    Review the application's dependency manifest, package.json, or SDK integration documentation where the Zoom Meeting SDK version is declared. The version is typically stored in the application's libraries or imported modules.
    Affected if The SDK version is below 6.0.0.
  5. Check Zoom Workplace VDI version
    Access the VDI environment and check the Zoom client version through the VDI client information panel, or consult the VDI admin console for the installed Zoom Workplace version.
    Affected if The installed VDI version is below 5.17.13.

You are affected if any installed Zoom product (Desktop, Rooms, SDK, Workplace, or VDI) matches the affected version ranges: below 6.0.0 for most products, or below 5.17.13 for Zoom Workplace VDI.

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.13 / 6.0.0 or later
Fixed in 5.17.136.0.0
Interim mitigation

Apply patches or updates provided by Zoom for affected Apps and SDK versions. Implement robust input validation and consider rate limiting on network endpoints to mitigate DoS conditions.

Recommended fix High confidence

Upgrade to Workplace Desktop 6.0.0, Meeting SDK 6.0.0, Rooms 6.0.0, Workplace 6.0.0, or Workplace VDI 5.17.13

  1. 1. Close all running Zoom applications (Workplace Desktop, Rooms, or any Zoom apps)
  2. 2. Download the latest version of the affected Zoom product from the official Zoom website (www.zoom.com)
  3. 3. Run the installer and follow the on-screen prompts to upgrade to version 6.0.0 or later
  4. 4. For Workplace Virtual Desktop Infrastructure, upgrade to version 5.17.13 or later
  5. 5. After installation completes, restart the Zoom application
  6. 6. Verify the installed version matches the fixed release (6.0.0 or 5.17.13 for VDI)
Caveat Review Zoom release notes for version 6.0.0 for any feature changes or migration requirements from previous versions

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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