CVE-2023-34114
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 · uneditedExposure of resource to wrong sphere in Zoom for Windows and Zoom for MacOS clients before 5.14.10 may allow an authenticated user to potentially enable information disclosure via network access.
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 confidenceThis is an access control vulnerability (CWE-284 Exposure of Resource to Wrong Sphere) in Zoom client software for Windows and MacOS versions prior to 5.14.10. An authenticated user with network access can potentially access information resources outside their intended security context, leading to unauthorized information disclosure.
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.14.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 version on WindowsOpen Zoom client, click your profile picture or initials in the top right, then click 'Check for Updates' or go to Help > About Zoom. Alternatively, right-click the Zoom shortcut, select Properties, and view the 'Details' tab for version information.Affected if The displayed version number is lower than 5.14.10
-
Check Zoom version on macOSOpen the Zoom client, click 'Zoom' in the menu bar, then select 'About Zoom' or 'Check for Updates'. Alternatively, navigate to the Applications folder, right-click Zoom.app, select 'Get Info', and view the version number under the 'General' section.Affected if The displayed version number is lower than 5.14.10
-
Check Zoom version via installer or installed programs listOn Windows, open Control Panel > Programs and Features (or Settings > Apps > Installed apps), locate 'Zoom' in the list, and note the version column. On macOS, open Terminal and run: defaults read /Applications/zoom.us.app/Contents/Info CFBundleShortVersionStringAffected if The listed version is lower than 5.14.10
If the Zoom client version installed on the Windows or MacOS system is 5.14.10 or higher, the system is not affected by this vulnerability; versions below 5.14.10 are affected.
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.14.10
Upgrade Zoom clients to version 5.14.10 or later to remediate this vulnerability. Organizations should inventory all Zoom client installations and deploy the patched version across the enterprise.
5.14.10 or later
- Open the Zoom desktop application
- Navigate to Zoom's account or help menu
- Select 'Check for Updates' or 'Download Latest Version'
- Download and install Zoom version 5.14.10 or later
- Restart the Zoom client after installation
- Verify the installed version matches or exceeds 5.14.10
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34114 — 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-2023-34114 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