Skip to content
Fencer Intel
high 7.9

CVE-2022-22782 json

Local privilege escalation in Windows Zoom Clients

published 4y ago modified 4mo ago also EUVD-2022-27925

cvss
7.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

The 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.

Patch / fix

  • Zoom Video Communications Inc Zoom Client for Meetings for Windows 5.9.7
  • Zoom Video Communications Inc Zoom Rooms for Conference Room for Windows 5.10.0
  • Zoom Video Communications Inc Zoom Plugins for Microsoft Outlook for Windows 5.10.3
  • Zoom Video Communications Inc Zoom VDI Windows Meeting Clients 5.9.6

Is CVE-2022-22782 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.9 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 2.0 6.6 AV:L/AC:L/Au:N/C:N/I:C/A:C

Affected products

  • Zoom Video Communications Inc Zoom Client for Meetings for Windows
  • Zoom Video Communications Inc Zoom Rooms for Conference Room for Windows
  • Zoom Video Communications Inc Zoom Plugins for Microsoft Outlook for Windows
  • Zoom Video Communications Inc Zoom VDI Windows Meeting Clients

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.