Skip to content
Fencer Intel
high 8.1

CVE-2022-22784 json

Improper XML Parsing in Zoom Client for Meetings

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

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
4.1%
EPSS 4.1% chance of exploitation in 30 days, percentile 90%
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 parse XML stanzas in XMPP messages. This can allow a malicious user to break out of the current XMPP message context and create a new message context to have the receiving users client perform a variety of actions.This issue could be used in a more sophisticated attack to forge XMPP messages from the server.

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-22784 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

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

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.5 AV:N/AC:L/Au:S/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

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.