Workplace DesktopApplication · Zoom
CVE-2025-30668
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 · uneditedInteger underflow in some Zoom Workplace Apps 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 confidenceAn integer underflow vulnerability in Zoom Workplace Apps allows an authenticated user to trigger a denial of service condition through network access. The flaw occurs when arithmetic operations produce results below the minimum representable integer value, leading to unexpected behavior that can crash or disable the application.
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.4.0< 6.4.0< 6.4.0< 6.4.0< 6.4.0< 6.1.17>= 6.1.18, < 6.2.13>= 6.2.14, < 6.3.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
- 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 productCheck installed programs for Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, Zoom Meeting SDK, or Zoom Workplace VDIAffected if Any Zoom product from the affected list is installed
-
Determine installed version of Zoom productOpen Zoom application, go to Help > About, or check system-installed programs list for version numberAffected if Version number is returned as < 6.4.0 for desktop/SDK/rooms products, or falls within VDI ranges (< 6.1.17, 6.1.18 to < 6.2.13, or 6.2.14 to < 6.3.10)
-
Confirm network exposureVerify that the Zoom application accepts network connections from authenticated usersAffected if Network access is enabled and unauthenticated or untrusted users can authenticate to the Zoom service
User is affected if they have any Zoom product installed with a version below 6.4.0 (or specific VDI ranges) and the application accepts network connections from authenticated users, making them vulnerable to the integer underflow DoS condition.
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.176.2.136.3.10
Apply vendor-provided patches or updates to Zoom Workplace Apps as they become available. Until a patch is released, consider restricting network access to trusted authenticated users and monitoring for DoS indicators.
6.4.0 for most products; 6.1.17, 6.2.13, or 6.3.10 (depending on starting version) for Workplace VDI
- Identify the specific Zoom product in use (Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, Workplace, or Workplace VDI)
- Determine the current installed version of the product
- For Workplace Desktop, Meeting SDK, Rooms, Rooms Controller, or Workplace: Upgrade to version 6.4.0 or later
- For Workplace VDI: Determine which version range currently installed (check if < 6.1.17, or >= 6.1.18 and < 6.2.13, or >= 6.2.14 and < 6.3.10), then upgrade to the minimum fixed version in that range (6.1.17, 6.2.13, or 6.3.10 respectively), or upgrade to 6.4.0 for complete coverage
- Verify the upgrade was successful by checking the new version number
- Test that the application functions normally after the upgrade
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
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30668 — 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-2025-30668 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