dbcve.org
RoomsApplication · Zoom

CVE-2023-34118

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 privilege escalation vulnerability in Zoom Rooms for Windows versions prior to 5.14.5. An authenticated user with local access to the system can exploit improper privilege management to elevate their privileges beyond what their account should normally allow.

MitigationUpdate Zoom Rooms for Windows to version 5.14.5 or later to remediate this vulnerability.

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. Confirm Zoom Rooms for Windows is installed
    Check for Zoom Rooms installation on the Windows system. Look for Zoom Rooms in the list of installed programs via Windows Settings > Apps & features, or check the Program Files directory for Zoom Rooms folders.
    Affected if Zoom Rooms for Windows is not found on the system, then this CVE does not apply.
  2. Determine the installed Zoom Rooms version
    Open the Zoom Rooms application and navigate to Help > About Zoom Rooms, or right-click the Zoom Rooms icon and select About. The version number will be displayed in the dialog that opens.
    Affected if Unable to retrieve a version number means the installation status is unclear.
  3. Compare the installed version against the affected range
    Take the version number found in the previous step (for example, 5.14.0, 5.14.3, 5.14.5, etc.) and compare it numerically to version 5.14.5. Versions prior to 5.14.5 (such as 5.14.0 through 5.14.4) are affected. Version 5.14.5 and later are not affected.
    Affected if The installed version is less than 5.14.5 (for example, 5.14.0, 5.13.5, etc.), indicating the system is running a vulnerable version.
  4. Verify local authentication context
    This vulnerability requires an authenticated user with local access to the Windows system where Zoom Rooms is installed. Determine if the system allows local user accounts or shared access where non-administrator users can log in.
    Affected if The system permits local user authentication, which is the typical configuration for Zoom Rooms deployments, meaning the exploitation condition exists.

A user is affected if Zoom Rooms for Windows is installed with a version number lower than 5.14.5 and the system allows local user authentication.

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

Update Zoom Rooms for Windows to version 5.14.5 or later to remediate this vulnerability.

Recommended fix High confidence

Zoom Rooms for Windows version 5.14.5 or later

  1. 1. Check current Zoom Rooms for Windows version by opening the Zoom Rooms application and navigating to Help > About Zoom Rooms
  2. 2. If version is below 5.14.5, download Zoom Rooms for Windows version 5.14.5 or later from the official Zoom website (explore.zoom.us)
  3. 3. Run the installer as an administrator to apply the update
  4. 4. After installation, verify the version has been updated to 5.14.5 or later by checking Help > About Zoom Rooms

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

Fix this in Rooms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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