Process-memory disclosure via uninitialized name pointer
Published May 3, 2024 · Updated Jul 9, 2026
Information disclosure in LIEF before 0.15.0 allows local users to read process memory through the C Mach-O reader's name field. The Macho_Binary_t structure's name pointer is never initialized, yet macho_reader.c passes it to fprintf as a C string. Exploitation requires local execution and user interaction; the read can expose arbitrary process memory, while invalid pointers can crash the consuming process.
Summary
What happened
Information disclosure in LIEF before 0.15.0 allows local users to read process memory through the C Mach-O reader's name field. The Macho_Binary_t structure's name pointer is never initialized, yet macho_reader.c passes it to fprintf as a C string. Exploitation requires local execution and user interaction; the read can expose arbitrary process memory, while invalid pointers can crash the consuming process.
The record
- CVE
- CVE-2024-31636
- Published
- May 3, 2024
- Updated
- Jul 9, 2026
- Vendor
- LIEF Project
- Product
- LIEF
- Classifications
- CWE-457, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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.14.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.
Public exploit references
- Upstream issue 1038 proof of conceptproof of concept · demonstrated
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