dbcve.org
Meeting Software Development KitApplication · Zoom

CVE-2023-39210

MEDIUM · 5.5 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 5.15.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Cleartext storage of sensitive information in Zoom Client SDK for Windows before 5.15.0 may allow an authenticated user to enable an information disclosure via local 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 · high confidence

The Zoom Client SDK for Windows versions prior to 5.15.0 stores sensitive information in cleartext (unencrypted) on the local file system. An authenticated user with local access to the affected system can read this unencrypted sensitive data, leading to information disclosure.

MitigationUpdate Zoom Client SDK for Windows to version 5.15.0 or later. Review and rotate any credentials or sensitive data that may have been stored in cleartext prior to the update.

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
Meeting Software Development KitApplication
Affected:< 5.15.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Zoom Meeting SDK installation
    Search the system for Zoom Meeting SDK directories or files. Check common development directories such as C:\Program Files, C:\Program Files (x86), or the project's dependencies folder where the SDK may have been extracted.
    Affected if The Zoom Meeting SDK for Windows is found on the system
  2. Identify the SDK version
    Locate version information in the SDK files. Check for a version file, manifest, or right-click the main DLL/EXE in the SDK folder and view Properties > Details. The version may also be listed in a CHANGELOG, README, or SDK documentation file.
    Affected if The installed version cannot be determined or is shown as below 5.15.0
  3. Compare version to affected range
    If a version number is found, compare it to the affected range: any version prior to 5.15.0 is vulnerable. Common version strings to look for include 5.14.x, 5.13.x, 5.12.x, and earlier major versions.
    Affected if The installed version is 5.14.x or earlier, or any version shown as less than 5.15.0
  4. Verify SDK is in use
    Check if the Zoom Meeting SDK is actively referenced in the application's codebase or deployed as part of a Windows application. Review project dependencies, bin directories, or deployment packages that include the Zoom SDK.
    Affected if The vulnerable SDK version is deployed and the application stores or processes sensitive data using the SDK's features

If the Zoom Meeting SDK for Windows is installed and the version is identified as less than 5.15.0, the environment is affected by this cleartext storage vulnerability.

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.15.0 or later
Fixed in 5.15.0
Interim mitigation

Update Zoom Client SDK for Windows to version 5.15.0 or later. Review and rotate any credentials or sensitive data that may have been stored in cleartext prior to the update.

Recommended fix High confidence

Meeting SDK for Windows version 5.15.0 or later

  1. Identify all applications or products using the Zoom Meeting SDK for Windows
  2. Locate the current SDK version in use (check project dependencies, packages, or bundled libraries)
  3. Download Zoom Meeting SDK for Windows version 5.15.0 or later from official Zoom developer resources
  4. Replace the existing SDK files in your project with the updated version from the fixed release
  5. Update any package manager references (e.g., NuGet, Maven) to point to version 5.15.0 or newer if applicable
  6. Rebuild the application to ensure compatibility with the updated SDK
  7. Test the application functionality to verify the upgrade does not break existing features
  8. Redeploy the updated application to production environments

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

Fix this in Meeting Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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