CVE-2024-45422
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 Apps before version 6.2.0 may allow an unauthenticated 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 · high confidenceA denial-of-service vulnerability exists in certain Zoom Apps versions prior to 6.2.0 due to improper input validation. An unauthenticated attacker with network access can send specially crafted input to the affected Zoom Apps, causing them to become unresponsive or crash.
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< 6.2.0< 6.2.0< 6.2.0< 6.2.0< 6.2.0< 6.2.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 productsOn Windows, check Add/Remove Programs or the installation directory (typically C:\Users\%username%\AppData\Roaming\Zoom). On macOS, check /Applications for Zoom apps. List all installed Zoom applications.Affected if Any Zoom product from the affected list (Zoom Workplace Desktop, Zoom Meeting SDK, Zoom Rooms, Zoom Rooms Controller, Zoom Video SDK, or Zoom Workplace) is installed.
-
Check installed Zoom versionFor Zoom Workplace Desktop/Zoom Rooms: Open the Zoom client, click your profile picture, then click 'Check for Updates' or go to About > Version. Alternatively, right-click the Zoom icon in taskbar and select 'Check for updates'. For SDK products, check the version referenced in the project dependencies or the DLL/file version properties.Affected if The displayed version number is less than 6.2.0 (for example, 6.1.10, 6.0.5, etc.).
-
Verify Zoom Apps feature is in useIn the Zoom client, look for the 'Apps' tab in the top ribbon or sidebar. Check if any third-party Zoom Apps have been added or are running. For Zoom Rooms, check if the Rooms client has integrated apps enabled. For SDK implementations, check if the application embeds or runs Zoom Apps functionality.Affected if Zoom Apps feature is enabled, configured, or any third-party apps are installed within the Zoom environment.
-
Confirm network exposureDetermine if the affected Zoom client or SDK has network connectivity. Check firewall rules allowing outbound connections from Zoom processes (zoom.exe, ZoomRooms.exe, etc.). For SDK implementations, review whether the application accepts external network input.Affected if The affected Zoom product has network access and can receive external input from unauthenticated attackers.
You are affected if any Zoom product from the affected list is installed with a version lower than 6.2.0 AND the Zoom Apps feature is enabled or in use, and the system has network exposure.
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 · scoped6.2.0
Upgrade all Zoom Apps to version 6.2.0 or later. If immediate upgrading is not possible, consider restricting network access to the affected Zoom Apps until the update can be applied.
6.2.0 or later
- Upgrade Workplace Desktop to version 6.2.0 or later
- Upgrade Meeting Software Development Kit to version 6.2.0 or later
- Upgrade Rooms to version 6.2.0 or later
- Upgrade Rooms Controller to version 6.2.0 or later
- Upgrade Video Software Development Kit to version 6.2.0 or later
- Upgrade Workplace to version 6.2.0 or later
- After upgrading, verify the Zoom Apps functionality to confirm the denial of service vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45422 — 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-45422 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