Workplace DesktopApplication · Zoom
CVE-2024-39822
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 · uneditedSensitive information exposure in some Zoom Workplace Apps, SDKs, Rooms Clients, and Rooms Controllers may allow an authenticated user to conduct an information disclosure 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 confidenceThis vulnerability allows an authenticated user to conduct information disclosure via network access in Zoom Workplace Apps, SDKs, Rooms Clients, and Rooms Controllers. The issue likely involves improper access controls or data exposure where user A can access user B's sensitive data, or unauthorized access to system information through network endpoints.
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
< 6.0.12< 6.0.12< 6.1.0< 6.1.0< 6.0.12CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 productOpen Zoom application and go to Help > About Zoom, or check Programs and Features in Control Panel to see which Zoom product is installed (Zoom Workplace Desktop, Zoom Rooms, or Zoom Rooms Controller)Affected if The installed product matches one of the affected products: Zoom Workplace Desktop, Zoom Meeting SDK, Zoom Rooms, or Zoom Rooms Controller
-
Check Zoom version numberIn the Zoom application, go to Help > About Zoom to view the exact version number (e.g., 6.0.10, 5.17.5)Affected if The version is below 6.0.12 for Zoom Workplace Desktop/Zoom Workplace/Meeting SDK, or below 6.1.0 for Zoom Rooms/Zoom Rooms Controller
-
Verify Windows installer version (alternative check)Open PowerShell and run: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\Zoom*' | Select-Object DisplayName, DisplayVersionAffected if The displayed version is below 6.0.12 (for Zoom Workplace/Meeting SDK) or below 6.1.0 (for Zoom Rooms)
-
Check if Zoom is configured for network exposureOpen Zoom app > Settings > Share Screen > verify if 'Share to Zoom Rooms' or network-based sharing features are enabled. Also check if third-party cloud recording or file transfer features are activeAffected if Network sharing features or third-party integrations are enabled, as the vulnerability is exploitable via network access
-
Confirm authentication statusCheck if single sign-on (SSO) or enterprise authentication is in use for Zoom. Review Zoom admin portal settings under Users > User Management to confirm user authentication methodAffected if Multiple authenticated users exist in the Zoom deployment, as the flaw allows one authenticated user to access another user's data
A user is affected if they run any Zoom Workplace Desktop, Meeting SDK, Zoom Rooms, or Zoom Rooms Controller version below 6.0.12 (or 6.1.0 for Rooms products) and the application is accessible to multiple authenticated users over a network.
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 · scoped6.0.126.1.0
Apply Zoom's security updates for all affected products. Review and enforce proper authentication and authorization controls to ensure users can only access their own data and resources.
Upgrade to version 6.0.12 (Workroom Desktop, Meeting SDK, Workplace) or 6.1.0 (Rooms, Rooms Controller) depending on the affected product
- Identify the specific Zoom product from affected list: Workplace Desktop, Meeting Software Development Kit, Rooms, Rooms Controller, or Workplace
- Navigate to the Zoom download center or admin portal
- Download and install the appropriate updated version based on product type
- For Workplace Desktop: upgrade to version 6.0.12 or later
- For Meeting Software Development Kit: upgrade to version 6.0.12 or later
- For Rooms: upgrade to version 6.1.0 or later
- For Rooms Controller: upgrade to version 6.1.0 or later
- For Workplace: upgrade to version 6.0.12 or later
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
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39822 — 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-39822 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