Process crash via invalid Mach-O segment access
Published Sep 30, 2022 · Updated May 20, 2025
Improper input validation in LIEF 0.12.1 allows remote attackers to crash a consuming process by supplying a crafted Mach-O file. In parse_dyldinfo_generic_bind, the file reaches SegmentCommand::virtual_address with an invalid object address, causing a near-null read and segmentation fault. A target application must process the attacker-supplied file with LIEF; the demonstrated consequence is termination of that process without data disclosure or modification.
Summary
What happened
Improper input validation in LIEF 0.12.1 allows remote attackers to crash a consuming process by supplying a crafted Mach-O file. In parse_dyldinfo_generic_bind, the file reaches SegmentCommand::virtual_address with an invalid object address, causing a near-null read and segmentation fault. A target application must process the attacker-supplied file with LIEF; the demonstrated consequence is termination of that process without data disclosure or modification.
The record
- CVE
- CVE-2022-40923
- Published
- Sep 30, 2022
- Updated
- May 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2022CVE publishedPublication date reported by the CVE source.
- May 20, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- poc2.zip Mach-O crash 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