CVE-2023-28804

8.2 HIGH

📋 TL;DR

This vulnerability allows attackers to replace binaries in Zscaler Client Connector on Linux due to improper cryptographic signature verification. It affects Linux users running Zscaler Client Connector versions before 1.4.0.105, potentially enabling unauthorized code execution.

💻 Affected Systems

Products:
  • Zscaler Client Connector
Versions: All versions before 1.4.0.105
Operating Systems: Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects Linux versions of Zscaler Client Connector. Windows and macOS versions are not affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise through malicious binary replacement leading to persistent backdoor installation, credential theft, and lateral movement within the network.

🟠

Likely Case

Local privilege escalation allowing attackers to replace legitimate binaries with malicious ones, potentially gaining elevated privileges or maintaining persistence.

🟢

If Mitigated

Limited impact with proper access controls and monitoring, though binary replacement could still occur if attacker gains local access.

🌐 Internet-Facing: LOW - Requires local access to the system, not directly exploitable over the internet.
🏢 Internal Only: HIGH - Internal attackers or compromised accounts with local access can exploit this vulnerability to escalate privileges.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires local access to the system. The vulnerability involves improper signature verification which could be exploited by replacing binaries with malicious ones.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.4.0.105 and later

Vendor Advisory: https://help.zscaler.com/client-connector/client-connector-app-release-summary-2023

Restart Required: Yes

Instructions:

1. Download Zscaler Client Connector version 1.4.0.105 or later from official Zscaler sources. 2. Stop the Zscaler service. 3. Install the updated version. 4. Restart the service and verify functionality.

🔧 Temporary Workarounds

Restrict local access

linux

Limit local access to systems running vulnerable Zscaler Client Connector to trusted users only.

Monitor binary changes

linux

Implement file integrity monitoring to detect unauthorized changes to Zscaler binaries.

# Example using auditd
sudo auditctl -w /opt/zscaler -p wa -k zscaler_binaries

🧯 If You Can't Patch

  • Implement strict access controls to limit who can access systems with vulnerable Zscaler Client Connector
  • Deploy file integrity monitoring to detect unauthorized binary modifications

🔍 How to Verify

Check if Vulnerable:

Check the installed Zscaler Client Connector version. If version is earlier than 1.4.0.105, the system is vulnerable.

Check Version:

zscaler --version 2>/dev/null || cat /opt/zscaler/version.txt 2>/dev/null || dpkg -l | grep zscaler

Verify Fix Applied:

Verify that Zscaler Client Connector version is 1.4.0.105 or later and that the service is running properly.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected binary modifications in Zscaler directory
  • Failed signature verification attempts
  • Unauthorized process execution from Zscaler paths

Network Indicators:

  • Unusual outbound connections from Zscaler processes
  • DNS queries to suspicious domains from Zscaler context

SIEM Query:

process.name:"zscaler" AND (file.path:"/opt/zscaler/*" AND file.action:"modify")

🔗 References

📤 Share & Export