dbcve.org
MeetingsApplication · Zoom

CVE-2023-39204

HIGH · 7.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 5.14.13 / 5.15.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
Buffer overflow in some Zoom clients may allow an unauthenticated 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 confidence

A buffer overflow vulnerability exists in certain Zoom client applications. An unauthenticated remote attacker can exploit this flaw via network access to cause a denial of service condition, potentially crashing the affected client.

MitigationUpdate Zoom client installations to the latest patched version provided by Zoom. Organizations should ensure all Zoom clients are patched through their patch management processes.

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
MeetingsApplication
Affected:< 5.15.10
RoomsApplication
Affected:< 5.15.10
Video Software Development KitApplication
Affected:< 5.15.10
Virtual Desktop InfrastructureApplication
Affected:< 5.14.13>= 5.15.0, < 5.15.11
ZoomApplication
Affected:< 5.15.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. Identify installed Zoom product
    Check Programs and Features or the application name in the Zoom installation directory to determine if the affected product is Zoom Meetings, Zoom Rooms, Zoom VDI, or the Zoom Video SDK installed.
    Affected if Any of these Zoom products are installed on the system
  2. Check Zoom Meetings version
    Open the Zoom desktop client, click your profile picture, then click 'Check for Updates' or look in Help > About Zoom to view the installed version number.
    Affected if The installed version is lower than 5.15.10
  3. Check Zoom Rooms version
    Open the Zoom Rooms controller interface or access the Zoom Rooms admin portal to view the software version.
    Affected if The installed version is lower than 5.15.10
  4. Check Zoom VDI version
    Access the VDI environment or virtual desktop where Zoom is installed and check the client version through Help > About or the system information panel.
    Affected if The installed version is 5.14.13, or >= 5.15.0 but lower than 5.15.11
  5. Verify network exposure
    Check if the Zoom client is running and listening on network ports, as the vulnerability is exploitable via network access.
    Affected if The Zoom client is running and network-accessible to unauthenticated remote attackers

A system is affected if it runs any Zoom product (Meetings, Rooms, VDI, or SDK) with a version lower than the fixed versions (5.15.10 for most products, or 5.15.11 for VDI) and the client is network-accessible.

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.13 / 5.15.10 / 5.15.11 or later
Fixed in 5.14.135.15.105.15.11
Interim mitigation

Update Zoom client installations to the latest patched version provided by Zoom. Organizations should ensure all Zoom clients are patched through their patch management processes.

Recommended fix High confidence

Zoom Meetings/Room/SDK: upgrade to version 5.15.10 or later; Zoom VDI: upgrade to 5.14.13 or 5.15.11 or later

  1. 1. Open the Zoom desktop client or mobile app
  2. 2. Navigate to the version information (Desktop: click your profile picture > Settings > About; Mobile: tap Settings > About)
  3. 3. Note the current version number
  4. 4. Download the latest Zoom client from the official Zoom website (zoom.us) or your organization's software distribution point
  5. 5. Run the installer and follow the prompts to update to the latest version
  6. 6. Restart the Zoom client after installation completes
  7. 7. Verify the version now shows 5.15.10 or later
Caveat Standard Zoom update; may require re-authentication if using SSO; ensure meeting room hardware compatibility for Rooms product

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

Fix this in Meetings Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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