dbcve.org
Client ConnectorApplication · Zscaler

CVE-2024-23457

HIGH · 7.8 CVSS v3.1 Published 2024-05-01
Fix available
A fix is available. Upgrade to 4.2.0.209 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
The anti-tampering functionality of the Zscaler Client Connector can be disabled under certain conditions when an uninstall password is enforced. This affects Zscaler Client Connector on Windows prior to 4.2.0.209

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

The anti-tampering protection in Zscaler Client Connector for Windows can be bypassed under specific conditions when an uninstall password is enforced, allowing the security control to be disabled prior to version 4.2.0.209.

MitigationUpgrade Zscaler Client Connector on Windows to version 4.2.0.209 or later to remediate this anti-tampering bypass vulnerability.

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

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
    Check for Zscaler Client Connector in Windows Programs and Features (appwiz.cpl) or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Zscaler*'}
    Affected if Zscaler Client Connector appears in installed programs
  2. Determine installed version
    In Programs and Features, locate Zscaler Client Connector and note the version column, or run: (Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Zscaler*'}).Version
    Affected if Version number is lower than 4.2.0.209 (e.g., 4.1.x, 4.0.x, 3.x)
  3. Check if uninstall password is enforced
    Inspect Zscaler Client Connector settings, policy configuration, or Windows registry for password protection settings related to uninstall functionality. Look for entries indicating an uninstall password is required or enabled.
    Affected if An uninstall password or anti-tampering password is configured/enforced in the Zscaler Client Connector settings or group policy
  4. Confirm vulnerability applicability
    Review version and password configuration together: if version is below 4.2.0.209 AND an uninstall password is actively set, the anti-tampering bypass condition is met.
    Affected if Both conditions true: version < 4.2.0.209 AND uninstall password is enforced

Your environment is affected if Zscaler Client Connector version is below 4.2.0.209 and an uninstall password is configured, allowing the anti-tampering protection to be bypassed.

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.2.0.209 or later
Fixed in 4.2.0.209
Interim mitigation

Upgrade Zscaler Client Connector on Windows to version 4.2.0.209 or later to remediate this anti-tampering bypass vulnerability.

Recommended fix High confidence

4.2.0.209 or later

  1. 1. Verify the current version of Zscaler Client Connector installed on the Windows system
  2. 2. Navigate to the official Zscaler support portal (help.zscaler.com) to obtain the updated Client Connector version 4.2.0.209 or later
  3. 3. Download the installer for Zscaler Client Connector version 4.2.0.209 or newer
  4. 4. Run the installer with appropriate administrative privileges
  5. 5. Restart the system if prompted to complete the installation
  6. 6. Verify the installed version is 4.2.0.209 or later to confirm the patch was applied

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

Fix this in Client Connector Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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