Secret disclosure via oversized integrity buffer
Published Mar 29, 2024 · Updated Aug 2, 2024
Information disclosure in Electron Packager 18.3.0 allows remote attackers to recover Node.js heap data from a generated executable. The Windows resource-editing path passes the backing ArrayBuffer of a serialized ASAR-integrity Buffer, embedding bytes beyond the intended data. A build must enable ASAR integrity and package a Windows target; the extra 1–10 KB can expose environment variables or secret-file contents to anyone obtaining the executable.
Summary
What happened
Information disclosure in Electron Packager 18.3.0 allows remote attackers to recover Node.js heap data from a generated executable. The Windows resource-editing path passes the backing ArrayBuffer of a serialized ASAR-integrity Buffer, embedding bytes beyond the intended data. A build must enable ASAR integrity and package a Windows target; the extra 1–10 KB can expose environment variables or secret-file contents to anyone obtaining the executable.
The record
- CVE
- CVE-2024-29900
- Published
- Mar 29, 2024
- Updated
- Aug 2, 2024
- Vendor
- Electron
- Product
- Electron Packager
- Classifications
- CWE-402, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 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== 18.3.0
- Affected versionversion=18.3.0 <18.3.1
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