Host binding disclosure via nonopaque scope Proxy
Published Apr 18, 2025 · Updated Apr 21, 2025
Information disclosure in Endo SES before 1.12.0 allows remote attackers to read host lexical bindings through Compartment code. The Compartment scope Proxy exposes names absent from globalThis to the surrounding lexical scope instead of remaining fully opaque. Exposure requires a page or extension to evaluate attacker-controlled code after declaring top-level const, let, or class bindings, and disclosure is limited to those bindings.
Summary
What happened
Information disclosure in Endo SES before 1.12.0 allows remote attackers to read host lexical bindings through Compartment code. The Compartment scope Proxy exposes names absent from globalThis to the surrounding lexical scope instead of remaining fully opaque. Exposure requires a page or extension to evaluate attacker-controlled code after declaring top-level const, let, or class bindings, and disclosure is limited to those bindings.
The record
- CVE
- CVE-2025-32792
- Published
- Apr 18, 2025
- Updated
- Apr 21, 2025
- Vendor
- EndoJS
- Product
- Endo
- Classifications
- CWE-497, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 18, 2025CVE publishedPublication date reported by the CVE source.
- Apr 21, 2025Record 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=< 1.12.0
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