dbcve.org
Client ConnectorApplication · Zscaler

CVE-2023-41972

HIGH · 7.8 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to 4.3.0.121 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
In some rare cases, there is a password type validation missing in Revert Password check and for some features it could be disabled. Fixed Version: Win ZApp 4.3.0.121 and later.

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 · low confidence

This is a missing password type validation vulnerability in Win ZApp's Revert Password check functionality. In certain rare scenarios, password validation can be bypassed or disabled for specific features, potentially allowing unauthorized access. The vulnerability stems from insufficient validation logic that fails to properly enforce password type checks in all code paths.

MitigationUpgrade Win ZApp to version 4.3.0.121 or later. Until then, audit access controls and monitor for unauthorized password reset or revert attempts.

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

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. Identify Zscaler Client Connector version
    Open Windows Control Panel or Settings > Apps > Apps & Features and locate 'Zscaler Client Connector' or 'Win ZApp'. Note the installed version number.
    Affected if The installed version is lower than 4.3.0.121 (e.g., 4.2.x, 4.1.x, etc.)
  2. Verify Revert Password feature presence
    Check the Zscaler Client Connector client interface or configuration for the presence of a 'Revert Password' or password revert/reset functionality in the user interface or command-line options.
    Affected if The Revert Password feature is present and accessible in the installed version
  3. Inspect password validation configuration
    Examine Zscaler Client Connector configuration files or registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Zscaler or HKEY_CURRENT_USER\SOFTWARE\Zscaler for password-related settings such as password type, validation flags, or bypass options.
    Affected if Configuration shows password validation can be disabled, bypassed, or is set to a weak type (e.g., 'none', 'optional', or missing type enforcement)
  4. Check for associated services
    Review running services related to Zscaler (e.g., 'Zscaler Client Connector Service' or 'ZSCloud.exe') and examine their startup parameters or associated configuration files for password validation settings.
    Affected if Service configuration or parameters indicate password type validation is not enforced

A system is affected if Zscaler Client Connector version is below 4.3.0.121 AND the Revert Password feature exists and password type validation can be bypassed or is missing in the configuration.

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.3.0.121 or later
Fixed in 4.3.0.121
Interim mitigation

Upgrade Win ZApp to version 4.3.0.121 or later. Until then, audit access controls and monitor for unauthorized password reset or revert attempts.

Recommended fix High confidence

Win ZApp 4.3.0.121 or later

  1. Upgrade Zscaler Client Connector to version 4.3.0.121 or later
  2. Verify the upgrade was successful by checking the Client Connector version in the application UI or system information
  3. Ensure the Revert Password feature now properly validates password types as expected

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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