CVE-2023-39205
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 · uneditedImproper conditions check in Zoom Team Chat for Zoom clients may allow an authenticated 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 confidenceA vulnerability in Zoom Team Chat client allows an authenticated attacker to cause a denial of service by triggering an improper conditions check, resulting in service disruption 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.16.0< 1.9.0< 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 productOpen the Zoom client and check About > Version, or check Add/Remove Programs (Windows) or Applications folder (Mac) for installed Zoom applications. Look for Zoom Meetings, Zoom Video SDK components, Zoom VDI client, or standard Zoom client.Affected if Any Zoom product listed in the affected products is installed.
-
Determine the exact version numberIn the Zoom client, go to the profile picture or 'About' section and note the full version number (e.g., 5.15.10). For Zoom VDI or Video SDK, check the application details or system information where the Zoom component version is displayed.Affected if The version is lower than the affected ranges: < 5.16.0 for Meetings/Zoom, < 1.9.0 for Video SDK, < 5.14.13 or >= 5.15.0 and < 5.15.11 for VDI.
-
Verify Team Chat is accessibleIn the Zoom client, locate the Team Chat or Chat feature in the sidebar. Check if you can access chat channels, direct messages, or if the Team Chat module is listed as an available feature in your account.Affected if Team Chat is enabled and accessible in the client, as the vulnerability specifically affects the Team Chat component.
-
Check network exposureReview network configuration to determine if the Zoom client can receive network connections from other authenticated users. This includes checking firewall rules, VPN status, and whether you are in a managed enterprise environment where other users can send network messages to your client.Affected if The client has network accessibility that allows other authenticated users to send messages or trigger the improper conditions check.
You are affected if you have any Zoom product installed with a version below the affected ranges AND Team Chat is enabled and accessible in your environment.
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 · scoped1.9.05.14.135.15.11
Apply the latest Zoom client update to address the improper conditions check vulnerability in Team Chat.
Meetings 5.16.0 | Video SDK 1.9.0 | VDI 5.14.13 or 5.15.11 | Zoom client 5.16.0
- For Zoom Meetings: Upgrade to version 5.16.0 or later by downloading from zoom.us/download
- For Zoom Video Software Development Kit: Upgrade to version 1.9.0 or later
- For Zoom Virtual Desktop Infrastructure: Upgrade to version 5.14.13 or 5.15.11 or later (depending on your current branch)
- For Zoom client: Upgrade to version 5.16.0 or later
- Verify the upgrade was successful by checking the Zoom client About section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39205 — 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-39205 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