dbcve.org
Client ConnectorApplication · Zscaler

CVE-2023-41970

HIGH · 7.8 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 4.1.0.62 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
An Improper Validation of Integrity Check Value vulnerability in Zscaler Client Connector on Windows during the Repair App functionality may allow Local Execution of Code.This issue affects Client Connector on Windows: before 4.1.0.62.

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

Zscaler Client Connector for Windows contains an improper validation vulnerability in its Repair App functionality. The flaw allows a local attacker to execute arbitrary code due to insufficient validation of integrity check values during the repair process. This is a local privilege escalation/remote code execution vulnerability affecting versions prior to 4.1.0.62.

MitigationUpgrade Zscaler Client Connector to version 4.1.0.62 or later to remediate this vulnerability. Organizations should deploy the updated client across all Windows endpoints.

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.1.0.62

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. Verify Zscaler Client Connector is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'Zscaler Client Connector' in the installed programs list
    Affected if Zscaler Client Connector appears in the installed programs on the Windows endpoint
  2. Check the installed version number
    Right-click the Zscaler Client Connector application in the Start menu and select 'Properties', or check the version in Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Zscaler*"}' in PowerShell
    Affected if The displayed version number is lower than 4.1.0.62 (for example, 4.1.0.50, 4.0.x.x, or any version prior to 4.1.0.62)
  3. Locate the Repair App executable
    Navigate to the Zscaler Client Connector installation directory (typically C:\Program Files\Zscaler\ZSClient\ or C:\Program Files (x86)\Zscaler\ZSClient\) and look for an executable named RepairApp.exe or similar repair-related utility
    Affected if The Repair App or repair utility executable exists in the Zscaler installation folder
  4. Check user access to Repair functionality
    Attempt to locate and access the repair functionality through the Zscaler Client Connector UI or by examining the application's available commands and modules
    Affected if A Repair App feature is present and accessible to the local user account

A Windows endpoint is affected if Zscaler Client Connector is installed with a version number lower than 4.1.0.62 and the Repair App functionality is present on the system.

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.1.0.62 or later
Fixed in 4.1.0.62
Interim mitigation

Upgrade Zscaler Client Connector to version 4.1.0.62 or later to remediate this vulnerability. Organizations should deploy the updated client across all Windows endpoints.

Recommended fix High confidence

Client Connector version 4.1.0.62 or later

  1. Navigate to the Zscaler Client Connector download page or use the organization's software distribution system
  2. Download Zscaler Client Connector version 4.1.0.62 or later for Windows
  3. Run the installer with appropriate administrative privileges
  4. Follow the standard upgrade procedure for Zscaler Client Connector
  5. Verify the installation completed successfully by checking the Client Connector version in the application

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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