dbcve.org
Client ConnectorApplication · Zscaler

CVE-2023-41973

HIGH · 7.8 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to 4.3.0.121 or later.
See remediation →
80/100
Remediation priority · High
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
ZSATray passes the previousInstallerName as a config parameter to TrayManager, and TrayManager constructs the path and appends previousInstallerName to get the full path of the exe. Fixed Version: Win ZApp 4.3.0.121 and later.

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 confidence

This is a path traversal vulnerability in ZSATray where the previousInstallerName parameter is directly concatenated to construct an executable file path without sanitization. An attacker could potentially manipulate the previousInstallerName value to access arbitrary files on the system by using directory traversal sequences (e.g., ../../../').

MitigationUpgrade to Win ZApp version 4.3.0.121 or later. If upgrading is not immediately feasible, implement input validation on the previousInstallerName parameter to ensure it contains only expected/allowed characters and does not include path traversal sequences.

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
Client ConnectorApplication
Affected:< 4.3.0.121

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
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 checks

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

  1. Check if Zscaler Client Connector is installed
    Look for Zscaler Client Connector in installed programs (Windows: Add/Remove Programs, Programs and Features) or check for Zscaler-related services and processes running on the system
    Affected if The software is present on the system
  2. Determine the installed version
    Check the installed version of Zscaler Client Connector. This can typically be found in the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or by right-clicking the Zscaler executable and viewing Properties > Details. Compare your version against the affected range: versions prior to 4.3.0.121
    Affected if The installed version is lower than 4.3.0.121 (e.g., 4.2.x, 4.1.x, etc.)
  3. Verify if ZSATray component is present
    Look for the ZSATray process or service running on the system. This can be done via Task Manager, Process Explorer, or by checking running services related to Zscaler
    Affected if ZSATray is actively running as a process or service on the affected system
  4. Inspect ZSATray configuration for previousInstallerName
    Examine configuration files or registry keys associated with ZSATray for any previousInstallerName parameter value. If you have access to logs or configuration, look for instances where this parameter is set
    Affected if A previousInstallerName parameter exists and contains directory traversal sequences (such as ../ or ..\) or points to unexpected file paths

The system is affected if Zscaler Client Connector is installed with a version prior to 4.3.0.121 and the ZSATray component with the vulnerable parameter is in use.

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 4.3.0.121 or later
Fixed in 4.3.0.121
Interim mitigation

Upgrade to Win ZApp version 4.3.0.121 or later. If upgrading is not immediately feasible, implement input validation on the previousInstallerName parameter to ensure it contains only expected/allowed characters and does not include path traversal sequences.

Recommended fix High confidence

Win ZApp 4.3.0.121 or later

  1. Identify the current version of Zscaler Client Connector (ZSATray) installed on the system
  2. Navigate to the Zscaler official download portal or contact your Zscaler administrator to obtain version 4.3.0.121 or later
  3. Download the Zscaler Client Connector installer for Windows (Win ZApp)
  4. Close any running Zscaler applications (including ZSATray)
  5. Run the installer with appropriate administrative privileges
  6. Follow the installation wizard prompts to complete the upgrade
  7. Verify the installed version is 4.3.0.121 or later after installation completes
  8. Restart the system if prompted to ensure the tray manager component is properly initialized

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

Fix this in Client Connector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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