CVE-2023-39199
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 · uneditedCryptographic issues with In-Meeting Chat for some Zoom clients may allow a privileged user to conduct an information disclosure 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 cryptographic vulnerability in Zoom's In-Meeting Chat feature in certain client versions allows an authenticated, privileged user to potentially intercept or disclose chat message content through network access, likely due to weak encryption, improper key management, or flawed crypto implementation in the chat transport.
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< 5.16.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check Zoom Meetings client versionOpen Zoom desktop client, click your profile picture, then 'Check for Updates' or go to Help > About Zoom to view the installed version numberAffected if Version is below 5.16.0
-
Check Zoom Rooms versionOn the Zoom Rooms controller or display, sign out and the version number will be shown on the login screen, or access Zoom Rooms settings to find the versionAffected if Version is below 5.16.0
-
Check Zoom VDI client versionOpen the Zoom VDI client and navigate to Help > About, or right-click the Zoom icon in the system tray and select 'About Zoom'Affected if Version is below 5.14.13 OR (version is 5.15.0 through 5.15.10)
-
Confirm In-Meeting Chat is in useIn an active Zoom meeting, locate the chat panel on the right side of the meeting window. If chat messages are being sent or received, the feature is activeAffected if You regularly use or host meetings with chat enabled and your version is vulnerable
You are affected if you run any Zoom client (Meetings, Rooms, or VDI) with a version lower than 5.16.0 (or the specific VDI ranges) and participate in meetings where the In-Meeting Chat feature is used.
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
Ensure all Zoom clients are updated to the latest patched version; restrict elevated privileges in meetings to trusted participants and monitor for anomalous network behavior.
Meetings/Room/Zoom client: 5.16.0 or later; VDI: 5.14.13+ or 5.15.11+
- 1. Identify the affected Zoom product (Meetings, Rooms, VDI, or standard Zoom client) currently installed
- 2. For Zoom Meetings client: Upgrade to version 5.16.0 or later
- 3. For Zoom Rooms: Upgrade to version 5.16.0 or later
- 4. For Zoom VDI: If using version 5.14.x, upgrade to 5.14.13 or later; if using version 5.15.x, upgrade to 5.15.11 or later
- 5. For Zoom client (general): Upgrade to version 5.16.0 or later
- 6. Verify the upgrade was successful by checking the Zoom client version in the desktop application (click your profile picture > Check for Updates or About Zoom)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39199 — 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-39199 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