CVE-2022-36928
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 · uneditedZoom for Android clients before version 5.13.0 contain a path traversal vulnerability. A third party app could exploit this vulnerability to read and write to the Zoom application data directory.
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 path traversal vulnerability in Zoom for Android clients before version 5.13.0 allows a malicious third-party app installed on the same device to access Zoom's application data directory, potentially reading or modifying sensitive application data.
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.13.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Zoom for Android is installedCheck the device for the Zoom app. On Android, you can list installed packages using 'pm list packages | grep zoom' or check in Settings > Apps for 'Zoom - One Platform to Connect'Affected if The Zoom for Android app is present on the device
-
Determine installed Zoom versionOpen Google Play Store, search for Zoom, or go to Settings > Apps > Zoom > App info to view the version number. Alternatively, use 'dumpsys package com.zipow.videobox' to query the package version.Affected if The displayed version is lower than 5.13.0
-
Confirm path traversal conditionVerify that other third-party applications can potentially be installed or already exist on the same device. This vulnerability is exploitable when a malicious app shares the device with Zoom.Affected if A potentially untrusted third-party app exists on the same Android device as Zoom
If Zoom for Android version 5.13.0 or higher is installed, the device is not affected by this path traversal vulnerability.
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.13.0
Update Zoom for Android clients to version 5.13.0 or later to remediate the path traversal vulnerability.
Zoom for Android version 5.13.0
- Open the Google Play Store on your Android device
- Search for "Zoom" or locate the Zoom app in your installed applications
- Tap on the Zoom app and select "Update" to install version 5.13.0 or later
- Alternatively, enable automatic app updates in Google Play Store settings to ensure Zoom receives future security updates
- Verify the installed version by going to Zoom app settings > About > Version to confirm version 5.13.0 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36928 — 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-36928 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