CVE-2025-30670
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 memory handling where the application attempts to dereference a null pointer, leading to a crash.
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 productOpen Windows Programs and Features or check the application name in the Zoom installation directory (commonly C:\Program Files\Zoom or C:\Program Files (x86)\Zoom). Look for: Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Workplace Desktop, or Zoom Workplace VDI.Affected if The product is one of: Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Workplace Desktop, or Zoom Workplace VDI.
-
Determine installed versionRight-click the Zoom executable in the installation folder, select Properties, then view the Details tab for the File Version. Alternatively, open Zoom app, click your profile picture, and look under About Zoom for the version number.Affected if The version cannot be determined or is lower than the fixed versions.
-
Compare version to affected rangesMatch your installed version against these ranges: Zoom Meeting SDK / Zoom Workplace Desktop: < 6.3.10; Zoom Rooms / Zoom Rooms Controller: < 6.4.0; Zoom Workplace VDI: 6.1.16 or >= 6.1.17 but < 6.2.12.Affected if Your installed version falls within any of these ranges.
-
Verify network accessibilityCheck if the Zoom application has open network ports or is configured to accept remote connections. In Windows Firewall, review inbound rules for Zoom executables. Look for listening ports in netstat -an | findstr LISTENING related to Zoom processes.Affected if The application is accessible over the network (listening on ports or allowing remote connections).
-
Check for crash eventsOpen Windows Event Viewer, navigate to Windows Logs > Application, and filter for Error events with source 'Zoom' or application crash events around recent dates. Check for Event ID 1000 (Application Crash).Affected if Recent Zoom-related application crashes are logged in the Windows Event Viewer.
You are affected if you have any of the listed Zoom products installed with a version below the fixed releases AND the application is network-accessible, which could allow an authenticated attacker to trigger the null pointer dereference crash.
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 the vendor-supplied patch or update to the fixed version of Zoom Workplace Apps for Windows when released. Until then, limit network access to trusted authenticated users and monitor for application crashes.
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 installed from: Meeting SDK, Rooms, Rooms Controller, Workplace Desktop, or Workplace VDI
- 2. Determine the currently installed version of each product
- 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 (if currently between 6.1.17 and 6.2.11)
- 8. Download the updated versions from the official Zoom download center at www.zoom.com
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30670 — 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-30670 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