dbcve.org
Client ConnectorApplication · Zscaler

CVE-2024-23483

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-06
Fix available
A fix is available. Upgrade to 4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Input Validation vulnerability in Zscaler Client Connector on MacOS allows OS Command Injection. This issue affects Zscaler Client Connector on MacOS <4.2.

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

An improper input validation vulnerability in Zscaler Client Connector on macOS allows OS command injection, enabling remote attackers to execute arbitrary operating system commands on affected systems with elevated privileges.

MitigationUpgrade Zscaler Client Connector to version 4.2 or later on all affected macOS systems to remediate the command injection 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

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 on macOS
    Check for the application in /Applications folder or use command: ls /Applications/ | grep -i Zscaler
    Affected if The application is not found in the Applications folder, meaning the product is not installed
  2. Determine installed version via command line
    Use the following command: defaults read /Applications/Zscaler\ Client\ Connector.app/Contents/Info.plist CFBundleVersion or check via: mdls -name kMDItemVersion /Applications/Zscaler\ Client\ Connector.app
    Affected if The version returned is less than 4.2 (for example, 4.1.x, 4.0.x, or any version below 4.2)
  3. Check running processes
    Use command: ps aux | grep -i Zscaler to verify if the client connector service is currently running
    Affected if The process is running and the version is below 4.2, indicating the vulnerable version is active
  4. Check application bundle version directly
    Right-click Zscaler Client Connector.app, select Get Info, or use: cat /Applications/Zscaler\ Client\ Connector.app/Contents/Info.plist | grep -A1 CFBundleShortVersionString
    Affected if The ShortVersionString or BundleVersion shows a version number lower than 4.2

A system is affected if Zscaler Client Connector is installed on macOS and the installed version is any version prior to 4.2.

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

Upgrade Zscaler Client Connector to version 4.2 or later on all affected macOS systems to remediate the command injection vulnerability.

Recommended fix High confidence

Client Connector 4.2 (or later) for MacOS

  1. Check current Zscaler Client Connector version on MacOS (click the Zscaler icon in the menu bar, select About Client Connector)
  2. Navigate to help.zscaler.com or the official Zscaler download portal to obtain Zscaler Client Connector version 4.2 or later for MacOS
  3. Download the installer package for the fixed release
  4. Double-click the downloaded .pkg file to initiate installation
  5. Follow the on-screen prompts to complete the installation, granting necessary permissions when prompted
  6. Restart the Client Connector or reboot the Mac to ensure the update takes effect
  7. Verify the installed version shows 4.2 or later to confirm remediation
Caveat Review Zscaler release notes for any changes to functionality or system requirements before upgrading

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

Fix this in Client Connector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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