dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2023-39217

HIGH · 7.5 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 5.14.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Improper input validation in Zoom SDK’s before 5.14.10 may allow an unauthenticated user to enable 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 · high confidence

Improper input validation in Zoom SDK versions before 5.14.10 allows unauthenticated attackers to cause denial of service via network access. The vulnerability stems from insufficient validation of input data processed by the SDK, enabling attackers to send malicious requests that crash the service.

MitigationUpgrade Zoom SDK to version 5.14.10 or later. If immediate upgrade is not feasible, implement network-level rate limiting and firewall rules to restrict unauthorized access to the SDK interfaces.

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
Meeting Software Development KitApplication
Affected:< 5.14.10
Video Software Development KitApplication
Affected:< 5.14.10

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate installed Zoom SDK
    Search system for Zoom SDK components - look for directories containing 'ZoomSDK' or 'ZoomVideoSDK', check common installation paths like /opt/, /usr/local/, or project dependencies in node_modules, vendor folders, or similar
    Affected if Zoom Meeting SDK or Zoom Video SDK files are found on the system
  2. Identify SDK version
    Examine version metadata files (version.txt, manifest.json, or package.json with zoom sdk dependencies) in the SDK installation directory, or query the SDK programmatically via its version API if available
    Affected if Version number is lower than 5.14.10 for either Meeting SDK or Video SDK
  3. Verify network exposure
    Check if the SDK service ports are listening on network interfaces (using netstat, ss, or similar tools). Determine if the SDK exposes endpoints to remote connections rather than local-only
    Affected if The SDK is bound to accessible network addresses and accepts remote connections
  4. Confirm authentication state
    Review SDK configuration files or initialization code to verify whether authentication mechanisms are properly enforced for SDK endpoints
    Affected if Authentication is missing, disabled, or misconfigured for the SDK interfaces

You are affected if you have Zoom Meeting SDK or Video SDK installed with a version below 5.14.10 AND the SDK is exposed to network access without proper authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.14.10 or later
Fixed in 5.14.10
Interim mitigation

Upgrade Zoom SDK to version 5.14.10 or later. If immediate upgrade is not feasible, implement network-level rate limiting and firewall rules to restrict unauthorized access to the SDK interfaces.

Recommended fix High confidence

Zoom Meeting SDK and Video SDK version 5.14.10

  1. 1. Identify whether your application uses the Zoom Meeting SDK or Zoom Video SDK by checking your project dependencies
  2. 2. Check your current SDK version by examining your package.json, podfile, or build.gradle dependencies
  3. 3. Navigate to the official Zoom Developer SDK download page at https://explore.zoom.us/en/developer/sdk/
  4. 4. Download Zoom Meeting SDK version 5.14.10 or later (or Video SDK version 5.14.10 or later, depending on which you use)
  5. 5. Update your project's dependency to reference version 5.14.10 or later using your package manager (npm, yarn, Maven, CocoaPods, etc.)
  6. 6. Rebuild and test your application to verify the SDK upgrade does not introduce regressions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39217 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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