The Zscaler Client Connector for Windows prior to 2.1.2.74 had a stack based buffer…
Priority MEDIUM 46CWE-787Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.
Summary
The Zscaler Client Connector for Windows prior to 2.1.2.74 had a stack based buffer overflow when connecting to misconfigured TLS servers. An adversary would potentially have been able to execute arbitrary code with system privileges.
Why it matters now
EPSS 0.01891 79th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2020-11633
- 2026-10-03 Alias added: GHSA-4p36-pgfp-hv82
References
More Zscaler Client Connector vulnerabilities
- TI-2024-15528 Local Privilege Escalation via lack of input validation CVSS 3.1CRITICAL 9.8
- TI-2024-15526 Insecure MacOS code sign check fallback CVSS 3.1CRITICAL 9.8
- TI-2024-15505 Multiple Arbitrary Creates/Overwrites by link following CVSS 3.1CRITICAL 9.8
- TI-2023-13308 Out-of-bounds write to heap in pacparser CVSS 3.1CRITICAL 9.8
- TI-2023-13315 ZCC on Linux privilege escalation CVSS 3.1CRITICAL 9.8
- TI-2023-13314 Linux ZCC allows unsigned updates, allowing elevated Code Execution CVSS 3.1HIGH 8.2
Sources
- CVE-2020-11633 · CVE Program
- CVE-2020-11633 · NVD
- FIRST EPSS
- GHSA-4p36-pgfp-hv82 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences