RoomsApplication · Zoom

CVE-2023-36537

HIGH · 7.8 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 5.14.5 or later.
See remediation →
80/100
Remediation priority · High
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
Improper privilege management in Zoom Rooms for Windows before version 5.14.5 may allow an authenticated user to enable an escalation of privilege 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 · high confidence

This is a local privilege escalation vulnerability in Zoom Rooms for Windows versions prior to 5.14.5. An authenticated user with local access can exploit improper privilege management to elevate their privileges on the affected system. The vulnerability allows a standard user to gain higher-level permissions than intended by the application design.

MitigationUpgrade Zoom Rooms for Windows to version 5.14.5 or later. Organizations should deploy the update through their standard software distribution processes and verify successful installation across all affected endpoints.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Verify Zoom Rooms is installed
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\ZoomRooms for the ZoomRooms.exe binary
    Affected if Zoom Rooms is not installed on the system, this CVE does not apply
  2. Find installed Zoom Rooms version
    Right-click ZoomRooms.exe in C:\Program Files\ZoomRooms, select Properties, and check the File Version on the Details tab. Alternatively, run 'wmic product get name,version' or check HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ZoomRooms in the registry
    Affected if Unable to determine the version - manual investigation needed
  3. Compare version against vulnerable range
    Compare the installed version number to 5.14.5. The vulnerability affects all versions below 5.14.5
    Affected if Installed version is 5.14.4 or lower, meaning the version is prior to the fixed release 5.14.5
  4. Check local user access context
    Verify the system has standard user accounts present. This CVE allows a standard authenticated user to escalate privileges - confirm if non-admin user accounts exist on the machine
    Affected if Standard user accounts exist on the system and the Zoom Rooms version is below 5.14.5, the environment is affected by this privilege escalation flaw

The system is affected if Zoom Rooms for Windows is installed with a version number lower than 5.14.5 and the system has standard user accounts that could potentially exploit this privilege escalation vulnerability.

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.14.5 or later
Fixed in 5.14.5
Interim mitigation

Upgrade Zoom Rooms for Windows to version 5.14.5 or later. Organizations should deploy the update through their standard software distribution processes and verify successful installation across all affected endpoints.

Recommended fix High confidence

Zoom Rooms for Windows version 5.14.5

  1. Download Zoom Rooms for Windows version 5.14.5 or later from the official Zoom download center (explore.zoom.us)
  2. Apply the update by running the installer and following standard Zoom Rooms upgrade procedures
  3. Restart the Zoom Rooms service if not automatically restarted after the update

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

Fix this in Rooms Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-36537 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-36537 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