dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2023-36533

HIGH · 7.5 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 5.14.7 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
Uncontrolled resource consumption in Zoom SDKs before 5.14.7 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 · moderate confidence

Uncontrolled resource consumption in Zoom SDKs prior to version 5.14.7 allows unauthenticated attackers to exhaust server or client resources via network requests, leading to denial of service. The vulnerability stems from insufficient validation or throttling of incoming network traffic within the SDK components.

MitigationUpdate Zoom SDK installations to version 5.14.7 or later to remediate the uncontrolled resource consumption vulnerability.

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.7
Video Software Development KitApplication
Affected:< 5.14.7

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 Zoom SDK installations in your environment
    Search for Zoom SDK files and libraries in your project directories, application folders, or system libraries. Look for files named like 'zoom_sdk', 'ZoomSDK', or check your dependency manifests (package.json, requirements.txt, pom.xml, build.gradle) for zoom-related packages.
    Affected if Zoom SDK libraries or dependencies are present in your environment
  2. Identify the installed Zoom Meeting SDK version
    Check the version of the Zoom Meeting SDK by examining the SDK library files, checking your dependency lock files, or running a package manager query (npm list, pip show, gradle dependencies) for zoom or meeting-sdk packages.
    Affected if The installed version is lower than 5.14.7 or cannot be determined to be 5.14.7 or higher
  3. Identify the installed Zoom Video SDK version
    Check the version of the Zoom Video SDK by examining SDK library files, dependency lock files, or running package manager queries for video-sdk or video-related zoom packages.
    Affected if The installed version is lower than 5.14.7 or cannot be determined to be 5.14.7 or higher
  4. Verify if SDK network features are in use
    Review your application code and SDK configuration to confirm whether the Zoom SDK is configured to handle incoming network connections or process real-time video/audio streams, as these are the pathways for the resource exhaustion attack.
    Affected if The SDK is actively processing network traffic or media streams (this is the default operational mode of the SDK)

You are affected if your environment contains any Zoom Meeting SDK or Video SDK installation with a version lower than 5.14.7, and the SDK is configured to process network requests or media streams.

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.7 or later
Fixed in 5.14.7
Interim mitigation

Update Zoom SDK installations to version 5.14.7 or later to remediate the uncontrolled resource consumption vulnerability.

Recommended fix High confidence

5.14.7 or later

  1. 1. Identify all applications and systems that integrate Zoom Meeting SDK or Video SDK
  2. 2. Locate the Zoom SDK package dependencies in your project (e.g., package.json, pom.xml, requirements.txt, or similar dependency management files)
  3. 3. Check the current installed version of the Zoom SDK packages
  4. 4. Update the SDK packages to version 5.14.7 or later using your package manager (e.g., npm install, pip install, or Maven update)
  5. 5. Rebuild and test your application to ensure compatibility with the updated SDK
  6. 6. Deploy the updated application to production environments

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

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36533 — 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-36533 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