CVE-2023-41971
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 · uneditedAn Improper Link Resolution Before File Access ('Link Following') vulnerability in Zscaler Client Connector on Windows allows a system file to be overwritten.This issue affects Client Connector on Windows: before 3.7.
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 confidenceThis is a symlink/junction point attack vulnerability in Zscaler Client Connector for Windows that allows a local attacker to overwrite system files by exploiting improper link resolution. The attacker could potentially escalate privileges by tricking the application into following symbolic links or junction points to modify protected system files.
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< 3.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check installed Zscaler Client Connector versionOpen Windows Control Panel > Programs and Features and locate Zscaler Client Connector, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Zscaler*"}' in PowerShell to retrieve the version numberAffected if The installed version is any version below 3.7 (such as 3.6.x, 3.5.x, or earlier)
-
Verify Zscaler service executable pathOpen Services.msc, find the Zscaler service, right-click and select Properties to view the path to the executable binaryAffected if The service executable is present and running, indicating the vulnerable software is active on the system
-
Check for write permissions on Zscaler directoriesNavigate to the Zscaler installation directory (typically Program Files/Zscaler or ProgramData/Zscaler), right-click the folder, select Properties > Security, and verify which users or groups have Write or Modify permissionsAffected if Non-privileged users have write access to Zscaler directories, which could enable symlink or junction point manipulation
The environment is affected if Zscaler Client Connector version is below 3.7 and the application directories are writable by standard users, allowing a local attacker to create symlinks or junction points for privilege escalation.
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 · scoped3.7
Upgrade Zscaler Client Connector on Windows to version 3.7 or later to remediate this vulnerability.
Client Connector 3.7 for Windows
- Navigate to the Zscaler support portal at help.zscaler.com and download Client Connector version 3.7 or later for Windows
- Back up any existing Zscaler Client Connector configuration or custom settings if applicable
- Uninstall the current version of Zscaler Client Connector from the Windows system
- Install the downloaded Client Connector version 3.7 or later
- Restart the Windows system if prompted by the installer
- Verify the installed version by checking Help > About in the Client Connector interface to confirm version 3.7 or higher is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41971 — 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-41971 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