CVE-2022-36924
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 · uneditedThe Zoom Rooms Installer for Windows prior to 5.12.6 contains a local privilege escalation vulnerability. A local low-privileged user could exploit this vulnerability during the install process to escalate their privileges to the SYSTEM user.
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 confidenceThe Zoom Rooms Installer for Windows versions prior to 5.12.6 contains a local privilege escalation vulnerability. During the installation process, a low-privileged local user can manipulate the install flow to execute code at SYSTEM level, gaining full administrative control over the host.
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.12.6CVSS 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 Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, or check for C:\Program Files\Zoom Rooms directoryAffected if Zoom Rooms appears in installed programs or the installation directory exists
-
Find installed Zoom Rooms versionRight-click ZoomRooms.exe in the installation directory (typically C:\Program Files\Zoom Rooms\) and select Properties > Details, or run 'Get-Item "C:\Program Files\Zoom Rooms\ZoomRooms.exe" | Select-Object VersionInfo' in PowerShellAffected if The version displayed is lower than 5.12.6 or the file does not exist (not installed)
-
Query Zoom Rooms version via registryRun 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Zoom Rooms*"} | Select-Object DisplayVersion' in PowerShell, or check HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{Zoom Rooms GUID} for DisplayVersionAffected if The registry DisplayVersion value is less than 5.12.6 or the registry key does not exist for Zoom Rooms
If Zoom Rooms is installed and its version is below 5.12.6, the system was likely updated or installed using a vulnerable Zoom Rooms Installer for Windows version and is affected by CVE-2022-36924.
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.12.6
Upgrade Zoom Rooms Installer for Windows to version 5.12.6 or later to remediate this vulnerability.
5.12.6
- Download Zoom Rooms Installer version 5.12.6 or later from the official Zoom website (explore.zoom.us)
- Apply the update to Zoom Rooms for Windows following standard Zoom update procedures
- Verify the installation completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36924 — 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-2022-36924 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