Cyber Resilience

CVE-2023-28802

Zscaler Client Connector ≤ 4.2.0.149

Published
21 November 2023
Modified
06 January 2026
CVSS Score v3.1 4.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2023-28802 is a medium-severity Improper Validation of Integrity Check Value (CWE-354) vulnerability in Zscaler Client Connector. Its CVSS base score is 4.9 (Medium).

Operationally, ranked at the 14th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An Improper Validation of Integrity Check Value in Zscaler Client Connector on Windows allows an authenticated user to disable ZIA/ZPA by interrupting the service restart from Zscaler Diagnostics. This issue affects Client Connector: before 4.2.0.149.

CWE(s)
CWE-354

Related Threats

CVEs Like This One

CVE-2024-23461Same product: Zscaler Client Connector
CVE-2024-23462Same product: Zscaler Client Connector
CVE-2023-41970Same product: Zscaler Client Connector
CVE-2023-41972Same product: Zscaler Client Connector
CVE-2023-28805Same product: Zscaler Client Connector
CVE-2023-28796Same product: Zscaler Client Connector
CVE-2023-28803Same product: Zscaler Client Connector
CVE-2024-23464Same product: Zscaler Client Connector
CVE-2023-41971Same product: Zscaler Client Connector
CVE-2024-23459Same product: Zscaler Client Connector

Affected Assets

zscaler
client connector
≤ 4.2.0.149

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 10 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V10.4.12

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SA-18 Tamper Resistance and Detection
addresses: CWE-354

Proper validation of integrity check values is required for reliable tamper detection, directly reducing undetected modification risks.

SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver)
addresses: CWE-354

Requires validation of integrity check values on every resolution response, directly mitigating tampered or corrupted DNS data.

SC-33 Transmission Preparation Integrity
addresses: CWE-354

Control mandates proper validation of integrity values (checksums) on prepared data, making flawed validation of those checks ineffective for attackers.

SI-7 Software, Firmware, and Information Integrity
addresses: CWE-354

Requires use of proper integrity verification tools, reducing the chance an incorrect check value is accepted.

SR-9 Tamper Resistance and Detection
addresses: CWE-354

Requires proper validation of integrity mechanisms, directly mitigating flawed check-value handling.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
prevents

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data at rest.

PR.DS-02 mostly match
prevents

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data in transit.

ID.RA-09 partial match
prevents

Mandates pre-acquisition integrity assessment, addressing only the initial portion of the weakness lifecycle.

RC.RP-03 partial match
prevents

Requires verification of backup integrity, covering validation only within recovery scenarios.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Cryptographic controls mandate integrity mechanisms whose correct validation directly prevents CWE-354.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper implementation and validation of checksums or MACs.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect missing integrity validation but does not itself implement the control.

A.8.26 Application security requirements partial match
prevents

Application security requirements include integrity checks on messages and data, mitigating improper validation.

A.8.20 Networks security none match
none

Network security policies may require integrity protection on transit data, indirectly addressing the weakness.

Hardening callouts derived

Configuration rules from DISA STIG baselines that reduce the attack surface for weaknesses of the type cited by this CVE. Derived transitively via CVE→CWE→STIG over `controls_xwalks` (authoritative rows only).

Oracle Linux 8 (1 rule)
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. via CWE-354
Oracle Linux 9 (1 rule)
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. via CWE-354
RHEL 7 (1 rule)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. via CWE-354

References