Workplace DesktopApplication · Zoom
CVE-2024-45421
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 Apps may allow an authenticated user to conduct an escalation of privilege 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 exists in certain Zoom Apps that allows an authenticated user to elevate their privileges through network access. The flaw likely involves improper bounds checking when processing data, potentially enabling arbitrary code execution or privilege escalation beyond the user's assigned role.
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.2.0< 6.2.0< 6.2.0< 6.2.0< 6.2.0< 6.2.0< 6.1.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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 productOpen the Zoom application, click your profile picture, then click 'Check for Updates' or look in Help > About to see which Zoom product and exact version number is installedAffected if The installed product matches one of the affected products (Zoom Workplace Desktop, Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Video SDK, Zoom Workplace, or Zoom Workplace VDI) and the version is below 6.2.0 (or below 6.1.12 for VDI)
-
Compare version to affected rangesNote the full version number shown in the About dialog and compare it numerically against the affected versions: < 6.2.0 for most products, < 6.1.12 for Zoom Workplace VDIAffected if The version number is lower than 6.2.0 (or 6.1.12 for VDI)
-
Determine if Zoom Apps feature is usedIn the Zoom client, go to the Apps tab or home screen to see if any Zoom Apps are installed, enabled, or have been used in meetingsAffected if Zoom Apps are installed, enabled, or actively used in the environment
-
Check for authenticated user accessReview logs or user session data to determine if untrusted or less privileged users have network access to the Zoom client environmentAffected if Authenticated users with limited privileges have network access to systems running the Zoom application
You are affected if you run any of the listed Zoom products at a version below 6.2.0 (or 6.1.12 for VDI) and have Zoom Apps enabled or in use by authenticated users on your 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.1.126.2.0
Apply patches or updates provided by Zoom for affected applications. If no patch is available, review and harden the affected Zoom App code to ensure proper input validation and buffer boundary checks are implemented.
6.2.0 for most products; 6.1.12 for Workplace Virtual Desktop Infrastructure
- 1. Identify the specific Zoom product in use from the affected list (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Video SDK, Workplace, or Workplace VDI)
- 2. Check the current installed version of the Zoom product
- 3. For Workplace Virtual Desktop Infrastructure: upgrade to version 6.1.12 or later
- 4. For all other affected products (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Video SDK, Workplace): upgrade to version 6.2.0 or later
- 5. Verify the upgrade was successful by checking the new version number
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 / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45421 — 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-45421 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