dbcve.org
MeetingsApplication · Zoom

CVE-2022-22785

CRITICAL · 9.1 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to 5.10.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 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.

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 failed to properly restrict the scope of session cookies to Zoom domains. Session cookies with Zoom scope could be sent to malicious non-Zoom domains, potentially allowing attackers to steal session credentials and spoof legitimate Zoom users.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Zoom Meetings installation
    On Windows, open Programs and Features or check C:\Users\<username>\AppData\Roaming\Zoom\bin for Zoom.exe. On macOS, check /Applications for Zoom.app. On Linux, check your package manager or /opt/zoom.
    Affected if Zoom Meetings client is installed on the system
  2. Determine installed Zoom version on Windows
    Right-click Zoom.exe, select Properties, go to the Details tab, and read the File Version field. Alternatively, open Zoom and click Help > About Zoom.
    Affected if The displayed version is less than 5.10.0 (for example, 5.9.x, 5.8.x, or earlier)
  3. Determine installed Zoom version on macOS
    Right-click Zoom.app in Applications, select Get Info, and read the Version field. Alternatively, open Zoom and click Zoom > About Zoom.
    Affected if The displayed version is less than 5.10.0
  4. Confirm affected version range
    Compare your installed version number against the affected range. Version numbers follow format like 5.9.6, 5.10.0, etc. The vulnerability affects any version lower than 5.10.0.
    Affected if The installed version starts with 5.9, 5.8, 5.7, 5.6, or any earlier major version (for example, 5.4.x, 4.x)

You are affected if the Zoom Client for Meetings is installed and its version is below 5.10.0, as this allows session cookies to be sent to malicious non-Zoom domains.

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. Download the Zoom Client for Meetings version 5.10.0 or later from the official Zoom website (explore.zoom.us) or your organization's authorized software distribution channel
  2. Install or update the Zoom Client for Meetings to version 5.10.0 or later on all affected platforms (Android, iOS, Linux, macOS, Windows)
  3. After installation, verify the version by navigating to the Zoom app settings or help section and confirming the version number is 5.10.0 or higher

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

Fix this in Meetings Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22785 — 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-22785 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