dbcve.org
Meeting SdkApplication · Zoom

CVE-2024-24699

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 5.15.15 / 5.16.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Business logic error in some Zoom clients may allow an authenticated user to conduct 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 confidence

A business logic error in Zoom client software allows authenticated users to disclose information via network access. The vulnerability stems from improper handling of authenticated sessions or data flow within the client, enabling a logged-in user to access sensitive data they should not have visibility into.

MitigationApply network segmentation and least-privilege access controls to limit exposure; identify and upgrade to patched Zoom client versions; monitor for anomalous authenticated access patterns.

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
Meeting SdkApplication
Affected:< 5.16.5
RoomsApplication
Affected:< 5.17.0
Vdi Windows Meeting ClientsApplication
Affected:< 5.15.15> 5.15.15, < 5.16.10> 5.16.10, < 5.17.5
ZoomApplication
Affected:< 5.16.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Zoom product
    Check what Zoom software is running in your environment - determine if it is the standard Zoom client, Zoom Rooms, Zoom Meeting SDK, or Zoom VDI Windows Meeting Client. Look at installed programs, running processes, or consult your software inventory.
    Affected if The product is any of: Zoom Meeting SDK, Zoom Rooms, Zoom VDI Windows Meeting Clients, or standard Zoom client.
  2. Find the Zoom client version number
    For standard Zoom client: open the app, click your profile picture, then Help > About Zoom. For Zoom Rooms: check the controller or display interface. For Zoom SDK: check the application using the SDK or its manifest. For VDI clients: check through your VDI management console or the client about section.
    Affected if The exact version cannot be determined for comparison.
  3. Compare version against affected ranges
    Match your installed version to the affected ranges: Zoom Meeting SDK and standard Zoom client are affected below 5.16.5. Zoom Rooms is affected below 5.17.0. Zoom VDI Windows Meeting Clients have three ranges: below 5.15.15, between 5.15.15 and 5.16.10 (excluding both), or between 5.16.10 and 5.17.5 (excluding both).
    Affected if Your installed version falls within any of these vulnerable ranges.
  4. Confirm authenticated session capability
    Verify that the Zoom installation allows user login and authentication. The vulnerability requires an authenticated session to exploit - check if users can log in to the Zoom client with their credentials.
    Affected if Users can authenticate to the Zoom client and the version is in the affected range.

You are affected if you are running any Zoom Meeting SDK, Zoom Rooms, Zoom VDI Windows Meeting Client, or standard Zoom client version that matches the vulnerable version ranges AND users can authenticate to the client.

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.15.15 / 5.16.5 / 5.16.10 or later
Fixed in 5.15.155.16.55.16.10
Interim mitigation

Apply network segmentation and least-privilege access controls to limit exposure; identify and upgrade to patched Zoom client versions; monitor for anomalous authenticated access patterns.

Recommended fix High confidence

Minimum fixed versions: Meeting SDK 5.16.5, Rooms 5.17.0, VDI Windows Clients 5.17.5, Zoom client 5.16.5

  1. Upgrade Zoom client to version 5.16.5 or later
  2. Upgrade Zoom Meeting SDK to version 5.16.5 or later
  3. Upgrade Zoom Rooms to version 5.17.0 or later
  4. Upgrade Zoom VDI Windows Meeting Clients to version 5.17.5 or later
  5. After upgrading, verify the client version by checking About or Settings > Statistics

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

Fix this in Meeting Sdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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