dbcve.org
Client ConnectorApplication · Zscaler

CVE-2024-23458

HIGH · 7.8 CVSS v3.1 Published 2024-08-06
Fix available
A fix is available. Upgrade to 4.2.0.190 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
While copying individual autoupdater log files, reparse point check was missing which could result into crafted attacks, potentially leading to a local privilege escalation. This issue affects Zscaler Client Connector on Windows <4.2.0.190.

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

A reparse point check is missing in the Zscaler Client Connector autoupdater when copying individual log files on Windows. Reparse points (including symbolic links and junction points) can be crafted to redirect file operations to arbitrary locations, enabling a local attacker to escalate privileges by overwriting sensitive files or executing code in protected contexts.

MitigationUpdate Zscaler Client Connector to version 4.2.0.190 or later on all affected Windows systems. Prioritize systems with untrusted local users.

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

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 Programs and Features or check for the Zscaler Client Connector service/process in Task Manager. Look for 'Zscaler Client Connector' or 'Zscaler' in the installed software list.
    Affected if The software is present on the system
  2. Determine installed version of Zscaler Client Connector
    Check the installed version through Windows Programs and Features, or right-click the Zscaler Client Connector executable in Program Files and view Properties > Details. Compare the version number to the affected range: versions prior to 4.2.0.190 are affected.
    Affected if The installed version is lower than 4.2.0.190 (for example, 4.2.0.100, 4.1.x, or any version number less than 4.2.0.190)
  3. Confirm the autoupdater component is present
    Look for the Zscaler autoupdater functionality in the installation directory (typically under Program Files/Zscaler) or check for scheduled tasks related to Zscaler updates.
    Affected if The autoupdater component exists and is configured to run on the system
  4. Check for reparse point creation capability in log directories
    Examine the file system permissions on the Zscaler Client Connector log directories. Determine if low-privilege users can create symbolic links or junction points in those locations.
    Affected if Low-privilege users have write access to log directories where the autoupdater copies files, allowing them to create reparse points

A system is affected if Zscaler Client Connector version is lower than 4.2.0.190 and the autoupdater is present and accessible to local users who could exploit the missing reparse point validation.

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.190 or later
Fixed in 4.2.0.190
Interim mitigation

Update Zscaler Client Connector to version 4.2.0.190 or later on all affected Windows systems. Prioritize systems with untrusted local users.

Recommended fix High confidence

Zscaler Client Connector 4.2.0.190 or later

  1. Identify the current Zscaler Client Connector version installed on Windows systems
  2. Navigate to the Zscaler Client Connector download or update mechanism
  3. Upgrade Zscaler Client Connector to version 4.2.0.190 or later
  4. Verify the upgrade was successful by checking the installed version
  5. Ensure the autoupdater log copying functionality now includes proper reparse point validation

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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