CVE-2023-28797
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 · uneditedZscaler Client Connector for Windows before 4.1 writes/deletes a configuration file inside specific folders on the disk. A malicious user can replace the folder and execute code as a privileged user.
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 confidenceZscaler Client Connector for Windows before version 4.1 contains a local privilege escalation vulnerability where the application writes and deletes configuration files in specific folders on disk. A malicious local user can exploit this by replacing those folders (likely via symlink or junction attacks) to achieve arbitrary code execution with elevated privileges.
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< 4.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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.
-
Check if Zscaler Client Connector is installedOpen Windows Settings > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Zscaler*"}' in PowerShell to search for Zscaler-related software.Affected if Zscaler Client Connector appears in the installed programs list.
-
Identify the installed versionIn Programs and Features, click on Zscaler Client Connector to view the version. Alternatively, check the file version of the main executable (typically in C:\Program Files\Zscaler\ or C:\Program Files (x86)\Zscaler\) by right-clicking the .exe and selecting Properties > Details.Affected if A version number is displayed in the version field.
-
Compare version against the affected rangeCompare the identified version number to 4.1. Versions before 4.1 (such as 4.0.x, 3.x, etc.) are within the affected range. Version 4.1 and later are not affected.Affected if The installed version is a release before 4.1 (e.g., 4.0.0.38, 3.5.2.1).
The environment is affected if Zscaler Client Connector for Windows is installed with any version number lower than 4.1.
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 · scoped4.1
Upgrade Zscaler Client Connector for Windows to version 4.1 or later to remediate the improper folder handling vulnerability.
4.1
- Download Zscaler Client Connector version 4.1 or later from the official Zscaler download portal or support site
- Uninstall the current version of Zscaler Client Connector from Windows Add/Remove Programs or use the uninstaller
- Install the downloaded version 4.1 or later
- Restart the system if prompted
- Verify the installed version by opening Zscaler Client Connector and checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28797 — 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-28797 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