Server environment disclosure via serialized error stacks
Published Jun 7, 2024 · Updated Aug 2, 2024
Information disclosure in Ido Pesok zsa before 0.3.3 allows remote attackers to read server paths and usernames through action errors. ZodSafeFunction builds returned error objects by JSON-serializing customError.stack, sending stack contents from the server to the client even in production builds. Exposure requires a deployed Next.js server action to return a triggered error; the published impact is limited to environment details, with no reported data modification or code execution.
Summary
What happened
Information disclosure in Ido Pesok zsa before 0.3.3 allows remote attackers to read server paths and usernames through action errors. ZodSafeFunction builds returned error objects by JSON-serializing customError.stack, sending stack contents from the server to the client even in production builds. Exposure requires a deployed Next.js server action to return a triggered error; the published impact is limited to environment details, with no reported data modification or code execution.
The record
- CVE
- CVE-2024-37162
- Published
- Jun 7, 2024
- Updated
- Aug 2, 2024
- Vendor
- Ido Pesok
- Product
- zsa
- Classifications
- CWE-209
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 7, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo