CVE-2022-36927
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 · uneditedZoom Rooms for macOS clients before version 5.11.3 contain a local privilege escalation vulnerability. A local low-privileged user could exploit this vulnerability to escalate their privileges to root.
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 confidenceZoom Rooms for macOS before version 5.11.3 contains a local privilege escalation vulnerability where a low-privileged local user can gain root privileges. This is a client-side vulnerability affecting macOS installations of Zoom Rooms.
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.11.3CVSS 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.
-
Locate Zoom Rooms application on macOSOpen Finder, navigate to /Applications folder, or search for 'Zoom Rooms' using Spotlight (Cmd+Space). Confirm the Zoom Rooms application is installed.Affected if Zoom Rooms application is present on the macOS system
-
Check Zoom Rooms version via app interfaceOpen Zoom Rooms application. Navigate to the Zoom Rooms menu at the top-left of the screen, click 'About Zoom Rooms' to view the version number.Affected if The displayed version is lower than 5.11.3 (for example, 5.11.2, 5.10.x, or earlier)
-
Check Zoom Rooms version via command lineRun the following command in Terminal: defaults read /Applications/ZoomRooms.app/Contents/Info.plist CFBundleShortVersionStringAffected if The version output is less than 5.11.3 or the command returns an error indicating the app is not installed
-
Verify complete version stringRun: defaults read /Applications/ZoomRooms.app/Contents/Info.plist CFBundleVersion to see the full build number alongside the short version.Affected if The short version (CFBundleShortVersionString) is below 5.11.3 regardless of build number
If Zoom Rooms for macOS is installed and the version is anything less than 5.11.3, the system is affected by this local privilege escalation vulnerability.
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.11.3
Upgrade Zoom Rooms for macOS to version 5.11.3 or later to remediate this vulnerability.
Zoom Rooms for macOS version 5.11.3 or later
- 1. Check the current Zoom Rooms version on the macOS client by opening Zoom Rooms and navigating to the version information.
- 2. Download Zoom Rooms version 5.11.3 or later from the official Zoom website or your organization's Zoom admin portal.
- 3. Install the updated Zoom Rooms client on the macOS device.
- 4. Verify the installation completed successfully and confirm the version displays 5.11.3 or higher.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36927 — 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-36927 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