vciy

CVE-2023-41973

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Lack of input santization on Zscaler Client Connector enables arbitrary code execution

CVE-2023-419734 of 4 sources documented this
22

rank 22 = 0 + 20 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00313  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.8, from NVD  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 22

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 20

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 22

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$14,500over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$14,500 = $4.99M incident cost x 0.9280467328949208 exposure x 0.00313 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00313EPSSNOT IN KEVas of 2026-09-20
Severity7.3 HIGHreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2024-03-27, 810 days at 0.00, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

Microsoft WindowsCVE-2022-26500CVE-2024-57728CVE-2024-41713CVE-2023-47246CVE-2022-2792541973

This record is one instance of CWE-22, improper limitation of a pathname to a restricted directory ('path traversal'). The index holds 10301 prior instances of this class, 94 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Sources disagree here.

Severity score
Zscaler7.3 HIGHreceipt
NVD7.8 HIGHreceipt
What it costs
ZscalerComplete confidentiality and integrity loss; partial availability lossreceipt
NVDComplete confidentiality, integrity and availability lossreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Zscaler Client Connector? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality and integrity loss; partial availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')receipt
Published consequencesCWE-22: Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands; Integrity: Modify Files or Directories; Confidentiality: Read Files or Directories…[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in4.3.0.121receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.3 HIGHreceipt
CVSS, NVD7.8 HIGHreceipt
Exploit probability0.00313 · top 76% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byZscalerreceipt
Recorded changes17 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productZscaler Client Connectorreceipt
Published rangeszscaler client connector < 4.3.0.121receipt
Fixed in4.3.0.121receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

Attack path

Local accessrequires low privilegesZscaler Client ConnectorCWE-22 path traversalConfidentiality and integrity lossC:H / I:Hexploits CWE-22data compromise

What it is stated by the CNA

ZSATray passes the previousInstallerName as a config parameter to TrayManager, and TrayManager constructs the path and appends previousInstallerName to get the full path of the exe. Fixed Version: Win ZApp 4.3.0.121 and later. receipt

NVD's analysis a second authority

severity
7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-22
affected versions
zscaler client connector < 4.3.0.121
also scored by
[email protected] 7.3 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

The CNA scored it 7.3 and NVD 7.8. Both are shown because both were published; we do not pick one.

check it yourself help.zscaler.com receipt

Movement the material steps

27 Mar 20240.00043
17 Mar 20250.00057 · scoring model v2025.03.14
15 Jun 20260.00313 · scoring model v2026.06.15

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 17 observations
27 Mar 20240.00043
21 Apr 20240.00044
17 Mar 20250.00057
19 Mar 20250.00125
20 Mar 20250.00064
27 Mar 20250.00125
28 Mar 20250.00064
29 Mar 20250.00125
30 Mar 20250.00064
15 Apr 20250.00058
4 May 20250.00027
12 Jul 20250.00034
15 Aug 20250.00047
11 Oct 20250.00056
18 Nov 20250.0007
21 Nov 20250.00056
15 Jun 20260.00313

17 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00313Published2024-03-26Index as of2026-06-15

Exploit probability more than doubled between 2025-03-17 and 2025-03-19 (0.00057 → 0.00125) and the record had been public for 2 years, 2 months when this index was last written.

Published 2024-03-26 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-22, improper limitation of a pathname to a restricted directory ('path traversal'). The index holds 10301 prior instances of this class, 94 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2022-21999 · Microsoft Windows 10 Version 1809matches 7 of 9KEV listed · 2022receipt
CVE-2022-26500matches 6 of 8KEV listed · 2022receipt
CVE-2024-57728matches 5 of 8KEV listed · 2025receipt
CVE-2024-41713matches 5 of 8KEV listed · 2024receipt
CVE-2023-47246matches 5 of 8KEV listed · 2023receipt
CVE-2022-27925matches 5 of 8KEV listed · 2022receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

10301 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2023-41973.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.