dbcve.org
RoomsApplication · Zoom

CVE-2024-27240

HIGH · 7.8 CVSS v3.1 Published 2024-07-15
Fix available
A fix is available. Upgrade to 5.17.13 / 6.0.0 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Improper input validation in the installer for some Zoom Apps for Windows may allow an authenticated user to conduct a privilege escalation via local 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

Improper input validation in the Zoom Apps Windows installer allows an authenticated local user to elevate privileges. The vulnerability stems from the installer not properly sanitizing or validating inputs during the installation process, enabling a local attacker with valid credentials to gain higher-level system access.

MitigationApply vendor-supplied patches or updates to Zoom Apps for Windows once released. Until then, restrict installer execution permissions and monitor for unauthorized installer usage by standard users.

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
RoomsApplication
Affected:< 6.0.0
Workplace DesktopApplication
Affected:< 6.0.0
Workplace Virtual Desktop InfrastructureApplication
Affected:< 5.17.13

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

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

  1. Identify installed Zoom product
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell to list installed Zoom applications. Look for Zoom Rooms, Zoom Workplace Desktop, or Zoom Workplace VDI.
    Affected if Any of these Zoom products are listed with a version number below the affected ranges.
  2. Determine Zoom product version
    Right-click the Zoom executable (Zoom.exe for desktop, ZoomRooms.exe for Rooms) in Program Files, select Properties, then view the File Version tab. Alternatively, run the executable with --version or check the registry under the product's uninstall key for the DisplayVersion value.
    Affected if The version shown is below 6.0.0 for Zoom Rooms or Zoom Workplace Desktop, or below 5.17.13 for Zoom Workplace VDI.
  3. Check for Zoom Apps module usage
    Open the Zoom desktop client, click the Apps icon in the sidebar, or navigate to the Apps settings panel. Verify whether any Zoom Apps are installed or if the Apps feature has been accessed. For Zoom Rooms, check if Apps integration is enabled in the Rooms controller settings.
    Affected if Zoom Apps feature has been used or enabled, as the vulnerability exists in the Zoom Apps Windows installer component.
  4. Review local user account context
    Open Task Manager, go to the Users tab, or run 'whoami /all' in Command Prompt to see currently logged-on authenticated users. Check if standard (non-admin) local users have valid credentials on the system.
    Affected if Standard user accounts with valid credentials exist on the system, as the privilege escalation requires an authenticated local user to exploit the installer input validation flaw.

You are affected if a Zoom product (Rooms, Workplace Desktop, or Workplace VDI) is installed with a version below 6.0.0 (or 5.17.13 for VDI) and the local environment contains standard users with valid credentials who could run the vulnerable Zoom Apps installer.

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.17.13 / 6.0.0 or later
Fixed in 5.17.136.0.0
Interim mitigation

Apply vendor-supplied patches or updates to Zoom Apps for Windows once released. Until then, restrict installer execution permissions and monitor for unauthorized installer usage by standard users.

Recommended fix High confidence

Rooms: 6.0.0+ | Workplace Desktop: 6.0.0+ | Workplace VDI: 5.17.13+

  1. 1. Identify the affected Zoom product in your environment (Rooms, Workplace Desktop, or Workplace Virtual Desktop Infrastructure)
  2. 2. For Zoom Rooms: Upgrade to version 6.0.0 or later
  3. 3. For Zoom Workplace Desktop: Upgrade to version 6.0.0 or later
  4. 4. For Zoom Workplace Virtual Desktop Infrastructure: Upgrade to version 5.17.13 or later
  5. 5. Verify the upgrade was successful by checking the installed version in the Zoom client or admin portal
  6. 6. Ensure the fix is applied to all affected systems in your deployment

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

Fix this in Rooms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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