← Back to results
Vulnerability record · public intelligence
CVE-2024-37162
MEDIUM

Generation of Error Message Containing Sensitive Information in zsa

Published Jun 7, 2024 · Updated Oct 23, 2026 · Also known as GHSA-wjmj-h3xc-hxp8

Severity · CVSSMEDIUM · 4.0
Known exploitationNot listed
EPSS / likelihood0.29%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Generation of Error Message Containing Sensitive Information in zsa

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

All users are impacted. The zsa application transfers the parse error stack from the server to the client in production build mode. This can potentially reveal sensitive information about the server environment, such as the machine username and directory paths. An attacker could exploit this vulnerability to gain unauthorized access to sensitive server information. This information could be used to plan further attacks or gain a deeper understanding of the server infrastructure.

Potential impact

All users are impacted. The zsa application transfers the parse error stack from the server to the client in production build mode. This can potentially reveal sensitive information about the server environment, such as the machine username and directory paths. An attacker could exploit this vulnerability to gain unauthorized access to sensitive server information. This information could be used to plan further attacks or gain a deeper understanding of the server infrastructure.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
LOW
Confidence
Not available
Aliases
GHSA-wjmj-h3xc-hxp8

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗

Record history

Published Jun 7, 2024 · Last refreshed Oct 23, 2026