CVE-2023-39203
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 · uneditedUncontrolled resource consumption in Zoom Team Chat for Zoom Desktop Client for Windows and Zoom VDI Client may allow an unauthenticated user to conduct a disclosure of information 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 confidenceUncontrolled resource consumption vulnerability in Zoom Team Chat component of Zoom Desktop Client for Windows and Zoom VDI Client allows unauthenticated users to cause excessive resource usage leading to information disclosure via network access.
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< 5.14.13>= 5.15.0, < 5.15.11< 5.16.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Zoom productCheck if Zoom Desktop Client for Windows or Zoom VDI Client is installed. On Windows, open Control Panel > Programs and Features, or check for Zoom.exe in Program Files, or check the Zoom icon in the system tray.Affected if Either Zoom Desktop Client for Windows or Zoom VDI Client is installed
-
Check Zoom version numberIn Zoom Desktop Client, click your profile picture or the zoom icon, then go to Help > About Zoom. For Zoom VDI Client, check the version displayed in the client or via the VDI environment's application inventory.Affected if Version is < 5.14.13, or >= 5.15.0 and < 5.15.11 (for VDI), or < 5.16.0 (for Desktop Client for Windows)
-
Confirm Team Chat component is accessibleVerify that the Team Chat feature is available in the Zoom client. In the Zoom Desktop Client, locate the Team Chat icon in the left sidebar or navigation panel.Affected if Team Chat is present and accessible (the vulnerability is in this component)
If Zoom Desktop Client for Windows or Zoom VDI Client is installed with a version in the vulnerable ranges and Team Chat is accessible, the environment is affected by this CVE.
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 · scoped5.14.135.15.115.16.0
Apply vendor-provided security patches or update to the latest Zoom Desktop Client for Windows and Zoom VDI Client versions that address this vulnerability.
5.14.13 or 5.15.11 for VDI; 5.16.0 for Zoom Desktop Client for Windows and Zoom VDI Client
- Identify the installed Zoom product (Virtual Desktop Infrastructure, Zoom Desktop Client for Windows, or Zoom VDI Client)
- For Virtual Desktop Infrastructure: upgrade to version 5.14.13 or later if on 5.14.x branch, or upgrade to version 5.15.11 or later if on 5.15.x branch
- For Zoom Desktop Client for Windows: upgrade to version 5.16.0 or later
- For Zoom VDI Client: upgrade to version 5.16.0 or later
- Verify the upgrade was successful by checking the version number in the client
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39203 — 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-2023-39203 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