dbcve.org
MeetingsApplication · Zoom

CVE-2022-22784

HIGH · 8.1 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to 5.10.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
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.

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 confidence

The Zoom Client for Meetings fails to properly parse XML stanzas in XMPP messages, allowing an attacker to break out of the current XMPP message context and create a new message context. This XML parsing vulnerability could enable message forging and arbitrary actions on the victim's client.

MitigationUpgrade Zoom Client for Meetings to version 5.10.0 or later across all affected platforms (Android, iOS, Linux, macOS, Windows).

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
MeetingsApplication
Affected:< 5.10.0

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Zoom installation status
    On Windows, open Programs and Features or check C:\Program Files\Zoom\bin\zoom.exe. On macOS, check /Applications/Zoom.us.app. On Linux, run 'which zoom' or check package list. On mobile, check installed apps list.
    Affected if Zoom Client for Meetings is not installed on the system
  2. Determine installed Zoom version on Windows
    Open Zoom and click your profile picture > Settings > About > Version, or run: wmic datafile where "name='C:\\Program Files\\Zoom\\bin\\zoom.exe'" get Version
    Affected if Version displays as a number lower than 5.10.0
  3. Determine installed Zoom version on macOS
    Open Zoom > Zoom.us menu > About Zoom, or run: defaults read /Applications/Zoom.us.app/Contents/Info CFBundleShortVersionString
    Affected if Version displays as a number lower than 5.10.0
  4. Determine installed Zoom version on Linux
    Run 'zoom --version' or check installed package: dpkg -l zoom | grep ii or rpm -qa | grep zoom
    Affected if Version displays as a number lower than 5.10.0
  5. Determine installed Zoom version on mobile
    On Android, go to Settings > Apps > Zoom > Version. On iOS, go to Settings > Zoom > Version.
    Affected if Version displays as a number lower than 5.10.0

The environment is affected if Zoom Client for Meetings is installed with a version number less than 5.10.0, as this is the vulnerable version range for the XML parsing flaw in XMPP messaging.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.10.0 or later
Fixed in 5.10.0
Interim mitigation

Upgrade Zoom Client for Meetings to version 5.10.0 or later across all affected platforms (Android, iOS, Linux, macOS, Windows).

Recommended fix High confidence

5.10.0 or later

  1. Open the Zoom desktop client and navigate to Help → About Zoom to check your current version
  2. If the version is below 5.10.0, download the latest Zoom Client for Meetings from the official Zoom website (zoom.us)
  3. Install the downloaded update by following the on-screen installation prompts
  4. After installation, verify the version by checking Help → About Zoom again to confirm you are running version 5.10.0 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Meetings Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22784 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22784 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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