CVE-2025-30665
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 · uneditedNULL pointer dereference in some Zoom Workplace Apps for Windows 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 confidenceA NULL pointer dereference vulnerability exists in Zoom Workplace Apps for Windows. An authenticated user with network access can trigger this flaw, causing the application to crash and result in a denial of service condition.
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.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 productOpen Windows Programs and Features (appwiz.cpl) or check the Zoom application installed: Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, or look for Zoom Meeting SDK in applications that use it. For VDI, check the virtual desktop client configuration.Affected if Any Zoom product from the list is installed (Meeting SDK, Rooms, Rooms Controller, Workplace Desktop, or Workplace VDI)
-
Determine Zoom Workplace Desktop versionOpen Zoom Workplace Desktop app, click your profile picture or the gear icon, then select 'About Zoom' or 'Check for Updates' to view the exact version number (e.g., 6.x.x).Affected if Version is less than 6.4.0 (e.g., 6.3.10 or earlier)
-
Determine Zoom Rooms versionOpen the Zoom Rooms application, go to Settings or the room control interface, and locate the version information typically shown in the About or System Information section.Affected if Version is less than 6.4.0
-
Determine Zoom Rooms Controller versionOpen the Zoom Rooms Controller app on the designated controller device (tablet or touch panel), access the About or Settings menu to view the installed version.Affected if Version is less than 6.4.0
-
Determine Zoom Workplace VDI versionCheck the VDI client configuration or session information provided by your virtual infrastructure (VMware Horizon, Citrix, etc.) for the Zoom VDI component version, or contact your VDI administrator for the installed Zoom version.Affected if Version is less than 6.1.17, OR between 6.1.18 and 6.2.12 inclusive, OR between 6.2.14 and 6.3.9 inclusive
Your environment is affected if any installed Zoom product (Desktop, Rooms, Rooms Controller, Meeting SDK, or VDI) is running a version lower than 6.4.0, or if VDI falls into the specific vulnerable version ranges.
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 the Zoom vendor patch or update to the latest version of Zoom Workplace Apps for Windows. Organizations should verify all deployed instances are running the patched version.
Zoom Workplace Apps version 6.4.0 or later (VDI: 6.1.17+, 6.2.13+, or 6.3.10+)
- 1. Identify which Zoom product(s) are in use (Meeting SDK, Rooms, Rooms Controller, Workplace Desktop, or Workplace VDI)
- 2. Check the current installed version of the affected Zoom application
- 3. Download the fixed version from the official Zoom website (www.zoom.com) or your Zoom account portal
- 4. For Meeting SDK, Rooms, Rooms Controller, and Workplace Desktop: Upgrade to version 6.4.0 or later
- 5. For Workplace VDI: Upgrade to version 6.1.17 or later for the 6.1.x branch; 6.2.13 or later for the 6.2.x branch; 6.3.10 or later for the 6.3.x branch (or preferably the latest stable release)
- 6. Verify the upgrade was successful by checking the version number in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30665 — 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-30665 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