CVE-2023-39212
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 · uneditedUntrusted search path in Zoom Rooms for Windows before version 5.15.5 may allow an authenticated user to enable a denial of service 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 confidenceZoom Rooms for Windows versions before 5.15.5 contain an untrusted search path vulnerability that allows an authenticated local attacker to potentially trigger a denial of service by placing malicious files in a location where the application searches for resources or dependencies.
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.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 Rooms version on WindowsOpen Windows PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Zoom Rooms*'} | Select-Object DisplayName, DisplayVersionAffected if The DisplayVersion returned is empty or shows a version lower than 5.15.5
-
Verify Zoom Rooms version via executableLocate the ZoomRooms.exe executable (typically in C:\Program Files\Zoom Rooms or C:\Program Files (x86)\Zoom Rooms), right-click, select Properties, and inspect the File Version on the Details tabAffected if The file version shown is earlier than 5.15.5
-
Check application directory write permissionsOpen Command Prompt as administrator and run: icacls 'C:\Program Files\Zoom Rooms' (or the actual installation path found in step 2). Review the output for any permissions granted to Users or authenticated users that include (F) Full or (W) Write accessAffected if Standard user accounts or the Users group have Write or Full Control permissions on the Zoom Rooms installation directory
-
Check shared resources directory permissionsIf Zoom Rooms is installed to a shared network location or custom directory, run: icacls '<installation_path>' and verify whether non-admin users can write to folders where the application loads dependencies or resourcesAffected if Non-administrative users have Write permissions to directories the application uses for loading resources
You are affected if Zoom Rooms for Windows is installed at a version lower than 5.15.5 AND standard user accounts have Write permissions to the application installation directory or its resource folders.
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.5
Upgrade Zoom Rooms for Windows to version 5.15.5 or later to remediate this vulnerability. In enterprise deployments, verify the update across all conference room systems and ensure standard user accounts cannot write to application directories.
Zoom Rooms for Windows version 5.15.5 or later
- 1. Open Zoom Rooms application on Windows
- 2. Navigate to the Zoom Rooms menu and select 'Check for Updates' or open the Zoom Rooms Client settings
- 3. If an update is available, download and install Zoom Rooms version 5.15.5 or later
- 4. Alternatively, download the latest Zoom Rooms for Windows installer from the official Zoom website (explore.zoom.us)
- 5. Restart the Zoom Rooms application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39212 — 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-39212 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