CVE-2025-30671
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 in Zoom Workplace Apps for Windows allows an authenticated user to cause a denial of service via network access. The vulnerability stems from improper validation of pointer references in the application's network handling code, leading to a crash when an attacker triggers the dereference of a null pointer.
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.3.10< 6.4.0< 6.4.0< 6.3.10< 6.1.16>= 6.1.17, < 6.2.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
- 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 product typeOpen Zoom application and go to Help > About Zoom, or check Add/Remove Programs to see the exact product name (Zoom Workplace Desktop, Zoom Rooms, Zoom Rooms Controller, or Zoom Meeting SDK)Affected if The product is any of the Zoom variants listed in affected products
-
Check installed version numberIn the Zoom app, go to Help > About Zoom to view the exact version number. For Zoom Rooms, check the controller or sign-in portal. For SDK, check the application using it or review the SDK DLL version propertiesAffected if Version is below 6.3.10 for Desktop/SDK, below 6.4.0 for Rooms/Controller, or for VDI: 6.1.16 or any 6.1.17-6.2.11 version
-
Determine if network access is enabledCheck Zoom settings under Settings > Network to see if incoming connections are allowed, or review firewall rules that permit inbound traffic to Zoom processes (zoom.exe, ZoomRooms.exe, or related services)Affected if Network inbound access is permitted to Zoom processes from untrusted networks
-
Verify authentication controlsReview Zoom account settings and meeting/room security settings to confirm if-only-authenticated-users settings are enabled, and check if unknown or untrusted accounts have accessAffected if Meeting or room access allows unauthenticated or untrusted users to join via network
-
Monitor for crash logs or service disruptionsCheck Windows Event Viewer under Application logs for crash events related to Zoom (zoom.exe, ZoomUMX.exe), or review Zoom diagnostic logs in %appdata%\Zoom or %localappdata%\Zoom for null pointer or access violation errorsAffected if Recent crashes or access violations involving Zoom processes are logged
User is affected if running any of the listed Zoom products at a version below the fixed release AND the application accepts network connections from authenticated but potentially untrusted users.
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.166.2.126.3.10
Apply vendor-provided patches for Zoom Workplace Apps for Windows when released. Until then, restrict network access to trusted authenticated users only and monitor for service disruptions.
Meeting SDK: 6.3.10+ | Rooms: 6.4.0+ | Rooms Controller: 6.4.0+ | Workplace Desktop: 6.3.10+ | Workplace VDI: 6.2.12+
- 1. Identify which Zoom product(s) are in use from the affected list (Meeting SDK, Rooms, Rooms Controller, Workplace Desktop, or Workplace VDI)
- 2. Determine the current installed version of the affected Zoom application on Windows
- 3. For Meeting Software Development Kit: upgrade to version 6.3.10 or later
- 4. For Rooms: upgrade to version 6.4.0 or later
- 5. For Rooms Controller: upgrade to version 6.4.0 or later
- 6. For Workplace Desktop: upgrade to version 6.3.10 or later
- 7. For Workplace Virtual Desktop Infrastructure: upgrade to version 6.2.12 or later (or 6.1.16 if staying on that branch)
- 8. Download the updated version from the official Zoom website (www.zoom.com) or your organization's software distribution channel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30671 — 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-30671 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