Application crash via malformed Mach-O load command
Published Sep 13, 2022 · Updated Aug 3, 2024
Heap-buffer over-read in LIEF before 0.12.1 allows context-dependent attackers to crash macho_reader through a crafted Mach-O file. When a load command extends beyond available input, the parser retains its declared size after raw-data extraction fails, so print_binary reads past a one-byte heap allocation. Processing an attacker-supplied Mach-O file is required; the published reproducer terminates under AddressSanitizer, while broader code execution is not demonstrated.
Summary
What happened
Heap-buffer over-read in LIEF before 0.12.1 allows context-dependent attackers to crash macho_reader through a crafted Mach-O file. When a load command extends beyond available input, the parser retains its declared size after raw-data extraction fails, so print_binary reads past a one-byte heap allocation. Processing an attacker-supplied Mach-O file is required; the published reproducer terminates under AddressSanitizer, while broader code execution is not demonstrated.
The record
- CVE
- CVE-2022-38495
- Published
- Sep 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
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.
Weakness, pattern, technique
Public exploit references
- macho_reader crafted Mach-O 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