CVE-2022-22788
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 Opener installer is downloaded by a user from the Launch meeting page, when attempting to join a meeting without having the Zoom Meeting Client installed. The Zoom Opener installer for Zoom Client for Meetings before version 5.10.3 and Zoom Rooms for Conference Room for Windows before version 5.10.3 are susceptible to a DLL injection attack. This vulnerability could be used to run arbitrary code on the victims host.
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 Opener installer, downloaded when users attempt to join a meeting without Zoom installed, contains a DLL injection vulnerability in Zoom Client for Meetings and Zoom Rooms for Conference Room for Windows versions before 5.10.3. An attacker could exploit this to load malicious DLLs and execute arbitrary code on the victim's 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.10.3< 5.10.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Client for Meetings installationSearch for Zoom.exe in typical installation directories: C:\Program Files\Zoom\bin\ and %APPDATA%\Zoom\bin\. Use PowerShell command: Get-ChildItem -Path 'C:\Program Files\Zoom','$env:APPDATA\Zoom' -Recurse -Filter 'Zoom.exe' -ErrorAction SilentlyContinueAffected if Zoom.exe is found in either location
-
Determine Zoom Meetings versionRight-click Zoom.exe, select Properties, then view the Details tab to find the Product Version. Alternatively, run: (Get-Item 'C:\Program Files\Zoom\bin\Zoom.exe').VersionInfo.ProductVersionAffected if Version displayed is lower than 5.10.3 (e.g., 5.10.0, 5.9.x, etc.)
-
Locate Zoom Rooms installationSearch for ZoomRooms.exe in typical installation paths: C:\Program Files\ZoomRooms\ and C:\Program Files (x86)\ZoomRooms\. Use PowerShell: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)' -Recurse -Filter 'ZoomRooms.exe' -ErrorAction SilentlyContinueAffected if ZoomRooms.exe is found on the system
-
Determine Zoom Rooms versionRight-click ZoomRooms.exe, select Properties, then view the Details tab to view the Product Version. Or use: (Get-Item 'C:\Program Files\ZoomRooms\ZoomRooms.exe').VersionInfo.ProductVersionAffected if Version displayed is lower than 5.10.3
-
Identify Zoom Opener componentSearch for 'zoomopener.exe' or 'ZoomOpener.exe' on the system: Get-ChildItem -Path 'C:\' -Recurse -Filter 'zoomopener.exe' -ErrorAction SilentlyContinue. This component is typically downloaded when joining a meeting without Zoom installedAffected if Zoom Opener executable exists on the system (vulnerable if Zoom version is also < 5.10.3)
A Windows system is affected if Zoom Client for Meetings or Zoom Rooms is installed with a version number lower than 5.10.3, regardless of whether the Zoom Opener component is present.
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.10.3
Upgrade Zoom Client for Meetings and Zoom Rooms for Conference Room for Windows to version 5.10.3 or later to remediate this vulnerability.
Zoom Client for Meetings 5.10.3 or later / Zoom Rooms for Conference Room for Windows 5.10.3 or later
- 1. Open a web browser and navigate to the official Zoom download page at explore.zoom.us
- 2. Download the latest version of Zoom Client for Meetings or Zoom Rooms for Conference Room for Windows
- 3. If you currently have Zoom installed, uninstall the existing version from your system
- 4. Run the downloaded installer file (.exe) with administrator privileges
- 5. Follow the on-screen prompts to complete the installation
- 6. After installation, verify the version by opening Zoom and navigating to Help > About Zoom to confirm version 5.10.3 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22788 — 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-22788 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