CVE-2022-22782
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 Client for Meetings for Windows prior to version 5.9.7, Zoom Rooms for Conference Room for Windows prior to version 5.10.0, Zoom Plugins for Microsoft Outlook for Windows prior to version 5.10.3, and Zoom VDI Windows Meeting Clients prior to version 5.9.6; was susceptible to a local privilege escalation issue during the installer repair operation. A malicious actor could utilize this to potentially delete system level files or folders, causing integrity or availability issues on the user’s host machine.
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 confidenceA local privilege escalation vulnerability exists in the Windows installer repair operation of multiple Zoom client products. During the repair process, a malicious actor could manipulate the operation to delete system-level files or folders, causing integrity or availability impacts on the affected host machine.
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.9.7< 5.10.0< 5.9.6< 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 Zoom Meetings versionOpen Windows Settings > Apps > Apps & features, find 'Zoom Meetings' and view the version, or right-click the Zoom.exe file (typically in C:\Users\Username\AppData\Roaming\Zoom\bin or C:\Program Files\Zoom) and select Properties > Details to see the File VersionAffected if The installed version is less than 5.9.7
-
Check Zoom Rooms versionOpen Windows Settings > Apps > Apps & features, find 'Zoom Rooms' and view the version, or check the ZoomRooms.exe file version in C:\Program Files\ZoomRoomsAffected if The installed version is less than 5.10.0
-
Check Zoom VDI Client versionOpen Windows Settings > Apps > Apps & features, locate the Zoom VDI client entry and view the version, or check the executable version in the VDI installation directoryAffected if The installed version is less than 5.9.6
-
Check Zoom Plugin for Microsoft Outlook versionOpen Windows Settings > Apps > Apps & features, find 'Zoom Plugin for Microsoft Outlook' and view the version, or open Outlook and check the Zoom plugin version in File > Office Account > About Outlook if availableAffected if The installed version is less than 5.10.3
A user is affected if any Zoom client product (Meetings, Rooms, VDI, or Outlook plugin) is installed on Windows with a version below the corresponding fixed version for that product.
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.9.65.9.75.10.0
Upgrade Zoom client products to the fixed versions: Meetings client to 5.9.7 or later, Zoom Rooms to 5.10.0 or later, Outlook Plugins to 5.10.3 or later, and VDI clients to 5.9.6 or later.
Zoom Client for Meetings >= 5.9.7, Zoom Rooms for Conference Room >= 5.10.0, Zoom VDI Windows Meeting Client >= 5.9.6, Zoom Plugin for Microsoft Outlook >= 5.10.3
- 1. Identify which Zoom products are installed on the Windows machine (Zoom Client for Meetings, Zoom Rooms for Conference Room, Zoom VDI Windows Meeting Client, or Zoom Plugin for Microsoft Outlook)
- 2. Download the appropriate fixed version from the official Zoom website or your organization's Zoom admin portal
- 3. For Zoom Client for Meetings: Upgrade to version 5.9.7 or later
- 4. For Zoom Rooms for Conference Room: Upgrade to version 5.10.0 or later
- 5. For Zoom VDI Windows Meeting Client: Upgrade to version 5.9.6 or later
- 6. For Zoom Plugin for Microsoft Outlook: Upgrade to version 5.10.3 or later
- 7. Verify the installed version matches or exceeds the fixed version after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22782 — 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-22782 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