CVE-2023-36538
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 access control in Zoom Rooms for Windows before version 5.15.0 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 confidenceThis is a local privilege escalation vulnerability in Zoom Rooms for Windows. An authenticated user with local access can exploit improper access control to gain elevated privileges. The vulnerability exists in versions prior to 5.15.0.
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.15.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Zoom Rooms is installedOpen Windows Settings > Apps & Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Zoom Rooms*'}Affected if Zoom Rooms for Windows appears in the installed programs list
-
Retrieve installed Zoom Rooms versionIn the Zoom Rooms client, click the profile icon and view the version number. Alternatively, check the Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ZoomRooms or use: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Zoom Rooms*'}).DisplayVersionAffected if A version number is returned from the system
-
Compare version against vulnerable rangeCompare your installed version number to 5.15.0. Zoom Rooms versions prior to 5.15.0 are affected (e.g., 5.14.x, 5.13.x, etc.)Affected if Installed version is lower than 5.15.0 (for example, 5.14.10, 5.13.5, etc.)
-
Confirm local access requirementVerify that an attacker would have physical access or local user credentials to the Windows machine running Zoom RoomsAffected if The Zoom Rooms Windows system is accessible to users with local account credentials
A user is affected if Zoom Rooms for Windows is installed with a version lower than 5.15.0 and an attacker has local access to that 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.15.0
Upgrade Zoom Rooms for Windows to version 5.15.0 or later to remediate this vulnerability.
5.15.0
- Upgrade Zoom Rooms for Windows to version 5.15.0 or later
- Verify the installation by checking the Zoom Rooms application version to confirm the update was applied successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36538 — 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-2023-36538 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