CVE-2022-28755
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 · uneditedThe Zoom Client for Meetings (for Android, iOS, Linux, macOS, and Windows) before version 5.11.0 are susceptible to a URL parsing vulnerability. If a malicious Zoom meeting URL is opened, the malicious link may direct the user to connect to an arbitrary network address, leading to additional attacks including the potential for remote code execution through launching executables from arbitrary paths.
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 confidenceA URL parsing vulnerability in Zoom Client for Meetings (all platforms, versions before 5.11.0) allows malicious meeting URLs to redirect users to arbitrary network addresses. This could enable remote code execution by launching executables from attacker-controlled paths.
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< 5.10.7< 5.11.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Zoom Client for Meetings installed versionOpen Zoom client, click your profile picture or help > About Zoom to view the version number. On Windows, also check Add or Remove Programs. On macOS, right-click Zoom.app > Get Info.Affected if Version displayed is before 5.11.0 (or before 5.10.7 for VDI installations)
-
Identify if this is a Virtual Desktop Infrastructure installationCheck with your IT department or VDI administrator whether the Zoom client is running in a virtual desktop environment. VDI versions have specific deployment configurations.Affected if The installation is a VDI version and the version is below 5.10.7
-
Verify Zoom process and componentsOpen Task Manager (Windows) or Activity Monitor (macOS) and confirm the running Zoom process matches the installed version number from step 1.Affected if Running version differs from installed version, indicating an outdated component
-
Review auto-update settingsIn Zoom client settings, go to General > Automatically download updates. Check if updates are being applied.Affected if Auto-update is disabled or failing, allowing the vulnerable version to persist
You are affected if the installed Zoom Client for Meetings version is below 5.11.0 (or below 5.10.7 for VDI installations), as this allows malicious meeting URLs to redirect to arbitrary network addresses and potentially execute remote code.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.10.75.11.0
Update Zoom Client for Meetings to version 5.11.0 or later to remediate the URL parsing vulnerability.
Zoom Client for Meetings version 5.11.0 or later
- 1. Check current Zoom Client for Meetings version by opening the client and navigating to Help > About Zoom
- 2. If version is below 5.11.0, download Zoom Client for Meetings version 5.11.0 or later from the official Zoom website (zoom.us/download)
- 3. Close any active Zoom meetings and exit the Zoom application
- 4. Install the updated Zoom Client for Meetings by running the downloaded installer
- 5. Restart the Zoom application and verify the version is 5.11.0 or higher under Help > About Zoom
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28755 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28755 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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