RoomsApplication · Zoom

CVE-2023-36532

HIGH · 7.5 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 5.14.5 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
Buffer overflow in Zoom Clients before 5.14.5 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

A buffer overflow vulnerability in Zoom client software versions prior to 5.14.5 allows an unauthenticated attacker on the network to trigger a denial of service condition by sending specially crafted network traffic to the vulnerable client.

MitigationUpdate Zoom Clients to version 5.14.5 or later to remediate this 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
RoomsApplication
Affected:< 5.14.5
Virtual Desktop InfrastructureApplication
Affected:< 5.14.5
ZoomApplication
Affected:< 5.14.5

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. Identify installed Zoom product
    Open the Zoom application and navigate to Help > About Zoom, or check the installed programs list in your system's control panel to determine if Zoom Client, Zoom Rooms, or Zoom VDI is installed
    Affected if Any of these three Zoom products are installed (Zoom Client, Zoom Rooms, or Zoom VDI)
  2. Determine installed version number
    In the Zoom application, go to Help > About Zoom and note the version number displayed (format typically shows as 5.x.x). Alternatively, check the Windows Programs and Features list, macOS Applications folder, or Linux package manager for the installed Zoom package version
    Affected if A version number is found that is less than 5.14.5, or the version cannot be determined and the product is known to be installed
  3. Verify network connectivity is enabled
    Confirm that the Zoom client has network connectivity enabled and is configured to receive incoming connections or meetings. Check Zoom settings under Settings > General or Settings > Video to confirm the client is operational and connected to Zoom services
    Affected if The Zoom client is running with network connectivity, as the vulnerability is triggered by specially crafted network traffic sent to the client
  4. Confirm version is within vulnerable range
    Compare the identified version number against the affected range: any version prior to 5.14.5 (including 5.14.0 through 5.13.x and earlier) is vulnerable. Version 5.14.5 and later are patched
    Affected if The installed version is below 5.14.5 (for example, 5.13.10, 5.12.5, etc.)

You are affected if any Zoom product (Client, Rooms, or VDI) is installed with a version number less than 5.14.5 and the application has network connectivity enabled.

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

Update Zoom Clients to version 5.14.5 or later to remediate this vulnerability.

Recommended fix High confidence

Zoom Client 5.14.5 or later (for Rooms, VDI, and standard Zoom Client)

  1. Download Zoom Client version 5.14.5 or later from the official Zoom website (explore.zoom.us)
  2. For Zoom Rooms, update the Rooms client to version 5.14.5 or later
  3. For Virtual Desktop Infrastructure users, update the VDI client to version 5.14.5 or later
  4. Restart the Zoom client after updating to ensure the new version is fully applied
  5. Verify the installed version matches or exceeds 5.14.5

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

Fix this in Rooms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36532 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