CVE-2022-28763
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.12.2 is 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 session takeovers.
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 · moderate confidenceThe Zoom Client for Meetings contains a URL parsing vulnerability across all major platforms (Android, iOS, Linux, macOS, Windows). When a user opens a maliciously crafted Zoom meeting URL, the client improperly parses the URL and may direct the user to connect to an arbitrary network address. This improper handling can lead to session takeovers and additional attacks.
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.12.2< 5.12.2< 5.12.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check Zoom Meetings client versionOpen the Zoom Meetings client, then navigate to the 'Help' menu and select 'About Zoom' to view the installed version numberAffected if The displayed version is lower than 5.12.2
-
Check Zoom Rooms for Conference Rooms versionAccess the Zoom Rooms controller or sign in to the Zoom Rooms web portal and locate the version information in the device settings or status areaAffected if The installed version is lower than 5.12.2
-
Check Zoom Virtual Desktop Infrastructure versionLog into the Zoom VDI admin interface or check the version displayed in the VDI client connection windowAffected if The version shown is lower than 5.12.2
-
Compare all installed Zoom products against the thresholdFor each Zoom product deployed in your environment (client, rooms, VDI), record the exact version number and verify it meets or exceeds 5.12.2Affected if Any product is found to be below version 5.12.2
You are affected if any installed Zoom product (Meetings client, Zoom Rooms, or Zoom VDI) has a version number lower than 5.12.2, as the URL parsing flaw exists in those vulnerable versions.
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.12.2
Upgrade Zoom Client for Meetings to version 5.12.2 or later to remediate this vulnerability. Users should avoid clicking on untrusted or unsolicited Zoom meeting links.
5.12.2 or later
- Download the Zoom Client for Meetings version 5.12.2 or later from the official Zoom website (zoom.us) or your platform's app store
- Verify the current installed version by opening the Zoom desktop client, clicking your profile picture, and selecting 'Check for Updates'
- If an update is available, follow the on-screen prompts to install version 5.12.2 or later
- For Android and iOS mobile clients, open the respective app store (Google Play Store or Apple App Store), search for Zoom, and update to version 5.12.2 or later
- After updating, confirm the version by checking 'About Zoom' or the app store listing to ensure the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28763 — 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-28763 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