Workplace DesktopApplication · Zoom
CVE-2024-27245
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 · uneditedBuffer overflow 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 confidenceA buffer overflow vulnerability in Zoom Workplace Apps and SDKs allows authenticated users to cause a denial of service via network access. The vulnerability stems from improper bounds checking when processing network inputs, enabling an attacker to overflow a buffer and crash the application or service.
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
< 5.17.11< 5.17.11< 6.0.0< 5.17.11< 5.15.17>= 5.16.0, < 5.16.15>= 5.16.16, < 5.17.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Zoom product and versionOpen the Zoom application and navigate to Help > About Zoom (Desktop), or check the application properties/diagnostics for Zoom Rooms or VDI instances. Use 'zoom --version' or check the installed package version via system package manager if available.Affected if The installed version number is lower than 5.17.11 for Zoom Workplace Desktop, Meeting SDK, or Workplace; lower than 6.0.0 for Zoom Rooms; or matches the VDI ranges (below 5.15.17, 5.16.0-5.16.14, or 5.16.16-5.17.10)
-
Verify the Zoom service or client is runningCheck if the Zoom application or service is currently active. On Windows, open Task Manager and look for Zoom processes. On Mac, use Activity Monitor. For VDI/Rooms, check if the Zoom Rooms service or virtual desktop session is active.Affected if The Zoom application or service is running and accessible on the network, as the vulnerability is exploitable via network access
-
Confirm network accessibility of Zoom servicesDetermine if the Zoom installation has open network listeners or ports. Check firewall rules or port status using 'netstat -an' or system network utilities, looking for ports typically used by Zoom (typically 443, 80, or meeting-related ports).Affected if The Zoom installation accepts network connections from authenticated users, as the vulnerability is triggered via network input processing
-
Check for authenticated network access exposureEvaluate whether the Zoom environment permits network connections from users outside the local machine. For Zoom Rooms or VDI, verify if remote authenticated users can connect to the service.Affected if The Zoom installation allows authenticated remote users to send network inputs, as the CVE requires authenticated user access for exploitation
A user is affected if they are running any Zoom Workplace Desktop, Meeting SDK, Rooms, Workplace, or VDI version below the fixed releases (5.17.11, 6.0.0, or the specific VDI ranges) and the application accepts network connections from authenticated 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.175.16.155.17.11
Apply available Zoom patches or updates for affected Workplace Apps and SDK versions. Until patches are available, restrict network access to trusted authenticated users and monitor for unusual service disruptions.
5.17.11 (or 6.0.0 for Rooms; specific VDI versions as noted above)
- 1. Identify the affected Zoom product (Workplace Desktop, Meeting SDK, Rooms, or Workplace VDI) currently installed
- 2. For Workplace Desktop, Meeting SDK, or Workplace: upgrade to version 5.17.11 or later
- 3. For Rooms: upgrade to version 6.0.0 or later
- 4. For Workplace VDI: upgrade to version 5.15.17 or later; or if using 5.16.x, upgrade to 5.16.15 or later; or if using 5.16.16+, upgrade to 5.17.11 or later
- 5. Verify the installed version after upgrade to confirm the fix is applied
- 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
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27245 — 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-27245 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