Skip to content
Fencer Vulns
low 3.3

CVE-2022-28764 json

Local information exposure in Zoom Clients

published 2022-11-14 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-33203

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

Summary

The Zoom Client for Meetings (for Android, iOS, Linux, macOS, and Windows) before version 5.12.6 is susceptible to a local information exposure vulnerability. A failure to clear data from a local SQL database after a meeting ends and the usage of an insufficiently secure per-device key encrypting that database results in a local malicious user being able to obtain meeting information such as in-meeting chat for the previous meeting attended from that local user account.

Patch / fix

  • Zoom Video Communications Inc Zoom Client for Meetings (for Android, iOS, Linux, macOS, and Windows) 5.12.6
  • Zoom Video Communications Inc Zoom VDI Windows Meeting Clients 5.12.6
  • Zoom Video Communications Inc Zoom Rooms for Conference Room (for Android, iOS, Linux, macOS, and Windows) 5.12.6

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Zoom Video Communications Inc Zoom Client for Meetings (for Android, iOS, Linux, macOS, and Windows)
  • Zoom Video Communications Inc Zoom VDI Windows Meeting Clients
  • Zoom Video Communications Inc Zoom Rooms for Conference Room (for Android, iOS, Linux, macOS, and Windows)

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-459 Incomplete Cleanup

References

Sources

Fencer Vulns 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.