CVE-2023-39201
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 · uneditedUntrusted search path in CleanZoom before file date 07/24/2023 may allow a privileged user to conduct an escalation of privilege 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 · moderate confidenceCleanZoom before the July 24, 2023 release contains an untrusted search path vulnerability where the application uses potentially insecure paths to locate executables or libraries. A privileged local user can exploit this by placing malicious code in a location that CleanZoom will search, allowing execution with elevated privileges and achieving local privilege escalation.
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< 2023-07-24CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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.
-
Verify CleanZoom installationIdentify if Zoom CleanZoom is installed on the system by checking for the application in standard software installation locations or program directories.Affected if CleanZoom is present on the system
-
Determine installed CleanZoom versionLocate the installed CleanZoom version or build date and compare it to the July 24, 2023 release threshold.Affected if The installed version is dated before 2023-07-24 or the version number is lower than the release from that date
-
Identify CleanZoom installation directoryFind the directory from which CleanZoom executes and verify if it is located in a user-writable path such as a user home directory, temp folder, or shared network location.Affected if CleanZoom runs from a directory that non-privileged users can modify
-
Examine PATH and search orderReview the system PATH environment variable and any application-specific library/executable search paths to determine if user-writable directories are included in the search order.Affected if User-writable directories appear in the PATH or search paths used by CleanZoom
A system is affected if CleanZoom is installed with a version predating July 24, 2023 and runs from or searches in directories writable by lower-privilege users.
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 · scoped2023-07-24
Upgrade CleanZoom to a version released on or after 07/24/2023. If upgrading is not immediately possible, ensure the application runs from controlled directories and that user-writable locations are not in the PATH or search order.
CleanZoom version with file date 07/24/2023 or later
- Download the latest version of CleanZoom from the official Zoom source at explore.zoom.us
- Ensure the downloaded file has a date of 07/24/2023 or later
- Verify the file integrity if possible (e.g., check digital signatures if provided)
- Uninstall any existing older version of CleanZoom
- Install the newly downloaded updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39201 — 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-39201 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