Process crash via empty segment-offset map
Published Sep 13, 2022 · Updated Aug 3, 2024
NULL pointer dereference in LIEF before 0.12.1 allows local users to crash a consuming process by supplying a crafted Mach-O file. When the segment-offset map is empty, Binary::segment_from_offset dereferences its begin iterator during dyld bind parsing, and SegmentCommand::file_offset then reads near the null page. The target process must parse the malicious file; the demonstrated consequence is a crash, with no reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in LIEF before 0.12.1 allows local users to crash a consuming process by supplying a crafted Mach-O file. When the segment-offset map is empty, Binary::segment_from_offset dereferences its begin iterator during dyld bind parsing, and SegmentCommand::file_offset then reads near the null page. The target process must parse the malicious file; the demonstrated consequence is a crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2022-38307
- Published
- Sep 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 13, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Issue 764 proof-of-concept Mach-O fileproof 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