CVE-2024-24690
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 input validation in some 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 confidenceImproper input validation in Zoom client software allows an authenticated attacker to trigger a denial of service condition through specially crafted network input. The vulnerability requires valid user credentials for exploitation but can be exploited remotely over the network.
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.5< 5.17.0< 5.14.14> 5.14.14, < 5.15.12> 5.15.12, < 5.16.10< 5.16.5< 5.16.5CVSS 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 productCheck installed programs list for Zoom Meeting SDK, Zoom Rooms, Zoom VDI, Zoom Video SDK, or standard Zoom client. In Windows, open Control Panel > Programs and Features or check Add/Remove Programs. On macOS, check /Applications folder for Zoom apps.Affected if Any of the listed Zoom products are installed (Meeting SDK, Rooms, VDI Windows, Video SDK, or standard Zoom)
-
Determine installed version numberFor Zoom client: open the app, click your profile picture > About Zoom. For Zoom Rooms: check the controller or room PC > Zoom Rooms icon > about. For SDKs: check the application's documentation or DLL/file properties of the Zoom SDK components installed.Affected if Version cannot be determined or is lower than the affected ranges for the specific product
-
Compare against affected version rangesMatch the installed product type and version to these ranges: Meeting SDK < 5.16.5; Rooms < 5.17.0; VDI Windows < 5.14.14 OR > 5.14.14 AND < 5.15.12 OR > 5.15.12 AND < 5.16.10; Video SDK < 5.16.5; standard Zoom < 5.16.5Affected if Installed version falls within any of the listed vulnerable version ranges
-
Verify network exposureDetermine if the Zoom client/SDK is exposed to network connections from untrusted sources. For Zoom Rooms or servers, check network configuration and firewall rules. For client systems, assess whether they accept remote connections.Affected if System accepts network connections from other Zoom users or is used in networked meeting scenarios
-
Confirm authentication is in useVerify that user accounts are configured and required for Zoom access. Check if meetings require login or if the system is part of an organization account requiring authentication.Affected if Authenticated user accounts are configured (which is required for this vulnerability to be exploitable)
You are affected if a vulnerable Zoom product version is installed AND users with valid credentials can connect over the network to the affected system.
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.145.15.125.16.5
Organizations should ensure Zoom client software is updated to the latest version once patches are released. Network-based mitigations such as limiting unnecessary network exposure may reduce attack surface while awaiting official patches.
Upgrade to Zoom Meeting SDK 5.16.5, Rooms 5.17.0, Video SDK 5.16.5, Zoom client 5.16.5, or VDI Windows Meeting Client 5.14.14/5.15.12/5.16.10 as applicable
- 1. Identify which Zoom product(s) are in use (Meeting SDK, Rooms, VDI Windows Meeting Client, Video SDK, or Zoom client) and current version number
- 2. Determine the appropriate fixed version based on product: Meeting SDK upgrade to 5.16.5, Rooms upgrade to 5.17.0, Video SDK upgrade to 5.16.5, Zoom client upgrade to 5.16.5
- 3. For VDI Windows Meeting Clients, upgrade to 5.14.14 (if on 5.14.x), 5.15.12 (if on 5.15.x), or 5.16.10 (if on 5.16.x)
- 4. Download the updated version from the official Zoom website (www.zoom.us) or your Zoom account portal
- 5. Test the upgrade in a non-production environment before deploying
- 6. Deploy the upgrade to production systems
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24690 — 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-2024-24690 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