Workplace DesktopApplication · Zoom
CVE-2024-27246
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 · uneditedUse 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 confidenceA use-after-free vulnerability in Zoom Workplace Apps and SDKs allows an authenticated attacker to cause a denial of service by corrupting memory through accessing freed memory regions via network access.
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 installed Zoom product and versionOpen Zoom application, go to Help > About to view the exact version number. On Windows, also check Add or Remove Programs. On macOS, right-click Zoom.app > Get Info to see version.Affected if Version is not shown or cannot be determined - the product may be installed but version information is inaccessible
-
Confirm the specific Zoom product typeDetermine which Zoom product is installed: Zoom Workplace Desktop (standard client), Zoom Rooms (conference room system), Zoom Meeting SDK (developer kit), or Zoom Workplace VDI (virtual desktop). Check the product name in Add/Remove Programs, Applications folder, or the About dialog.Affected if Product is not one of the five affected products listed (Workplace Desktop, Meeting SDK, Rooms, Workplace, or Workplace VDI)
-
Compare version against affected rangesMatch the installed version to the affected ranges: Zoom Workplace Desktop < 5.17.11, Zoom Meeting SDK < 5.17.11, Zoom Rooms < 6.0.0, Zoom Workplace < 5.17.11. For Zoom Workplace VDI, check if version is < 5.15.17, OR >= 5.16.0 and < 5.16.15, OR >= 5.16.16 and < 5.17.11.Affected if Installed version falls within any of the vulnerable version ranges listed
-
Verify network exposure of the Zoom componentConfirm the Zoom client or service is accessible over network. For Zoom Rooms, check if the room controller or display system is network-connected. For VDI, verify the virtual desktop infrastructure is accessible.Affected if The vulnerable product version is installed AND the component is network-accessible, enabling an authenticated attacker to trigger the use-after-free condition
User is affected if they have any of the listed Zoom products installed with a version number below the specified thresholds AND the component is network-accessible to authenticated attackers.
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 vendor-supplied patches or update to the latest version of Zoom Workplace Apps and SDKs as soon as available.
Workplace Desktop/Workplace/Meeting SDK: 5.17.11 | Rooms: 6.0.0 | VDI: 5.15.17, 5.16.15, or 5.17.11 (per branch)
- For Workplace Desktop, Workplace, and Meeting Software Development Kit: Upgrade to version 5.17.11 or later
- For Rooms: Upgrade to version 6.0.0 or later
- For Workplace Virtual Desktop Infrastructure: Upgrade to version 5.15.17 or later; OR version 5.16.15 or later; OR version 5.17.11 or later (depending on your current branch)
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
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 locallyCheck whether your project pulls in CVE-2024-27246 — 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-27246 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