CVE-2024-45425
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 · uneditedIncorrect user management in some Zoom Workplace Apps may allow a privileged 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 confidenceIncorrect user management in Zoom Workplace Apps allows a privileged user to disclose information via network access. This appears to be a flaw in access controls within the user management functionality that permits information exposure beyond what the user's privileges should allow.
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.1.0< 6.1.0< 6.1.0< 6.1.0< 6.1.0< 6.1.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
- 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 product and versionOpen Zoom application, click your profile picture or initials in the top right, then look for 'Check for Updates' or go to Help > About Zoom to view the exact version number. Alternatively, on Windows check Programs and Features or the executable properties; on macOS check the app in Applications folder via Get Info.Affected if The installed version is below 6.1.0 for Desktop/Meeting SDK/Rooms/Rooms Controller/Workplace, or below 6.1.10 for Zoom Workplace VDI.
-
Determine if user management features are accessibleIn Zoom, navigate to the user management or administration panel. This is typically found under Settings > User Management (for account admins) or within the web portal at zoom.us under the Admin tab > User Management.Affected if A privileged user account exists and can access the user management interface, which indicates the vulnerable feature is present in the environment.
-
Verify presence of privileged user accountsIn the Zoom web portal or desktop client, check the Users or Team Members list to identify accounts with admin, owner, or elevated privileges. These are typically labeled as Admin, Owner, or have custom roles with elevated permissions.Affected if There are privileged user accounts configured in the Zoom environment, creating the condition for the access control flaw to be exploitable.
-
Check network exposure of Zoom servicesReview firewall rules, network segmentation, and VPN configurations to determine if the Zoom client or Zoom Rooms hardware has network access beyond the organization's controlled network. Check if ports used by Zoom (such as 443, 8801-8810 for video) are open to untrusted networks.Affected if The Zoom application or Zoom Rooms device has network access that could allow a privileged user to transmit disclosed information externally.
You are affected if your installed Zoom product version is below 6.1.0 (or 6.1.10 for VDI) and you have privileged user accounts with access to user management features over a network-accessible connection.
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.1.06.1.10
Apply the vendor patch/update for affected Zoom Workplace App versions. Review user permissions and implement least-privilege access controls as a defensive measure.
6.1.0 (or 6.1.10 for VDI)
- Identify the affected Zoom product from the list: Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI
- For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, and Workplace: upgrade to version 6.1.0 or later
- For Workplace Virtual Desktop Infrastructure: upgrade to version 6.1.10 or later
- After upgrading, verify the version by checking About/Version information in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.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 $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45425 — 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-45425 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