CVE-2024-39819
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 · uneditedIntegrity check in the installer for some Zoom Workplace Apps and SDKs for Windows may allow an authenticated user to conduct a privilege escalation via local 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 · high confidenceThis vulnerability exists in the installer for Zoom Workplace Apps and SDKs for Windows. An integrity check flaw in the installer allows an authenticated local user to perform privilege escalation, gaining elevated permissions they should not have.
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< 6.0.10< 5.17.13< 6.0.10CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/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 on WindowsOpen Windows Settings > Apps > Installed apps, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*, HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Zoom*'}Affected if A Zoom Meeting SDK, Zoom Rooms, or Zoom Workplace Desktop product is listed with a version number below 6.0.10 (for Meeting SDK or Workplace Desktop) or below 5.17.13 (for Zoom Rooms)
-
Verify exact version numberRight-click the Zoom application in the installed apps list and select Advanced, or use the Zoom app itself: Click the user profile picture > Check for Updates to see current versionAffected if The displayed version is less than 6.0.10 for Zoom Meeting SDK or Zoom Workplace Desktop, or less than 5.17.13 for Zoom Rooms
-
Confirm Windows installer vulnerability contextCheck the Zoom installer package in Program Files (typically C:\Program Files\Zoom or C:\Program Files (x86)\Zoom) for the installer executable (e.g., ZoomInstaller.exe, ZoomSetup.exe) and note its file version via right-click > Properties > DetailsAffected if The installer file version is present and corresponds to an unpatched Zoom product version in the affected ranges
A system is affected if any Zoom product (Meeting SDK, Rooms, or Workplace Desktop) for Windows is installed with a version lower than 6.0.10 (or 5.17.13 for Zoom Rooms), since the installer integrity check flaw could allow local privilege escalation.
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.17.136.0.10
Update Zoom Workplace Apps and SDKs for Windows to the patched version provided by Zoom. Verify that the update is successfully applied across all affected systems.
Meeting SDK: 6.0.10+ | Rooms: 5.17.13+ | Workplace Desktop: 6.0.10+
- 1. Identify which Zoom product(s) are installed: Meeting Software Development Kit, Rooms, or Workplace Desktop for Windows
- 2. For Meeting Software Development Kit users: upgrade to version 6.0.10 or later
- 3. For Rooms users: upgrade to version 5.17.13 or later
- 4. For Workplace Desktop users: upgrade to version 6.0.10 or later
- 5. Download the updated installer from the official Zoom website (www.zoom.com) or your organization's Zoom admin portal
- 6. Run the installer with appropriate privileges and follow the standard upgrade procedure
- 7. Verify the installed version matches or exceeds the minimum fixed version for your product
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39819 — 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-39819 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