Skip to content
Fencer Intel
medium 5.9

CVE-2022-22785 json

Improperly constrained session cookies in Zoom Client for Meetings

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

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

Summary

The Zoom Client for Meetings (for Android, iOS, Linux, MacOS, and Windows) before version 5.10.0 failed to properly constrain client session cookies to Zoom domains. This issue could be used in a more sophisticated attack to send an unsuspecting users Zoom-scoped session cookies to a non-Zoom domain. This could potentially allow for spoofing of a Zoom user.

Patch / fix

  • Zoom Video Communications Inc Zoom Client for Meetings for Android 5.10.0
  • Zoom Video Communications Inc Zoom Client for Meetings for iOS 5.10.0
  • Zoom Video Communications Inc Zoom Client for Meetings for Linux 5.10.0
  • Zoom Video Communications Inc Zoom Client for Meetings for MacOS 5.10.0
  • Zoom Video Communications Inc Zoom Client for Meetings for Windows 5.10.0

Is CVE-2022-22785 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

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

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:L
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N

Affected products

  • Zoom Video Communications Inc Zoom Client for Meetings for Android
  • Zoom Video Communications Inc Zoom Client for Meetings for iOS
  • Zoom Video Communications Inc Zoom Client for Meetings for Linux
  • Zoom Video Communications Inc Zoom Client for Meetings for MacOS
  • Zoom Video Communications Inc Zoom Client for Meetings for Windows

Classification

Weakness
  • CWE-565 Reliance on Cookies without Validation and Integrity Checking

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.