dbcve.org
MeetingsApplication · Zoom

CVE-2022-22780

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 5.6.3 / 5.7.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 chat functionality was susceptible to Zip bombing attacks in the following product versions: Android before version 5.8.6, iOS before version 5.9.0, Linux before version 5.8.6, macOS before version 5.7.3, and Windows before version 5.6.3. This could lead to availability issues on the client host by exhausting system resources.

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 chat functionality was vulnerable to Zip Bomb attacks. An attacker could send a specially crafted compressed file that expands to an extremely large size when extracted, causing the client to exhaust system resources (disk space, memory, or CPU) and become unavailable.

MitigationUpdate Zoom clients to the patched versions: Android 5.8.6+, iOS 5.9.0+, Linux 5.8.6+, macOS 5.7.3+, Windows 5.6.3+. Consider implementing additional controls such as limiting attachment sizes or scanning files before extraction.

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.6.3< 5.7.3< 5.8.6< 5.9.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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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. Verify Zoom is installed
    Open Zoom client, click your profile picture or initials, then click 'Check for Updates' or look in the application menu for version information. On Windows, you can also right-click the Zoom icon and select 'Check for Updates'. On macOS, check in Zoom app under 'Zoom.us' menu > 'About Zoom'.
    Affected if Zoom is not installed or the client cannot be found, then the vulnerability does not apply
  2. Identify installed Zoom version
    In the Zoom client, click your profile picture or initials, then look for version information displayed (typically at the bottom or in 'About' section). Alternatively, check the Windows installer path: C:\Program Files\Zoom\bin\Zoom.exe right-click > Properties > Details > File Version, or on macOS: /Applications/zoom.us.app right-click > Show Package Contents > Info.plist for CFBundleShortVersionString.
    Affected if Unable to determine the installed version, assume potential vulnerability
  3. Compare version against affected ranges
    Compare your installed version number to these vulnerable ranges: versions before 5.6.3 (Windows), before 5.7.3 (macOS), before 5.8.6 (Windows/Linux), or before 5.9.0 (iOS/Android). The specific version you have must fall into one of these unpatched ranges.
    Affected if Your installed version is lower than 5.6.3, or between 5.6.3 and 5.7.2 (macOS only), or between 5.7.3 and 5.8.5 (Windows/Linux), or between 5.8.6 and 5.8.x (Android only), or before 5.9.0 (iOS)
  4. Confirm chat functionality usage
    This vulnerability affects the chat feature specifically. In Zoom, click the 'Chat' tab in the left sidebar to see if chat is accessible. The vulnerability triggers when receiving a crafted compressed file attachment via chat.
    Affected if Chat is available and you receive files from other meeting participants - the vulnerability could be triggered by a malicious compressed file sent to you

You are affected if your installed Zoom client version falls below 5.6.3 (Windows), 5.7.3 (macOS), 5.8.6 (Linux), or 5.9.0 (mobile), and you use the chat feature to receive file attachments.

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.6.3 / 5.7.3 / 5.8.6 or later
Fixed in 5.6.35.7.35.8.6
Interim mitigation

Update Zoom clients to the patched versions: Android 5.8.6+, iOS 5.9.0+, Linux 5.8.6+, macOS 5.7.3+, Windows 5.6.3+. Consider implementing additional controls such as limiting attachment sizes or scanning files before extraction.

Recommended fix High confidence

Windows: 5.6.3+, macOS: 5.7.3+, Linux: 5.8.6+, Android: 5.8.6+, iOS: 5.9.0+

  1. Open Zoom client and navigate to Help > Check for Updates (or use zoom.us website for manual download)
  2. Download and install the latest version for your platform: Windows 5.6.3+, macOS 5.7.3+, Linux 5.8.6+, Android 5.8.6+, or iOS 5.9.0+
  3. Restart the Zoom client after update installation
  4. Verify the installed version matches or exceeds the fixed release for your platform

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

Fix this in Meetings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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