Parser crash via unterminated process filename
Published Sep 13, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in LIEF commit 5d1d643 allows attackers to crash the parser by supplying a crafted ELF core file. CorePrPsInfo::parse_ treats the fixed-width pr_fname field as a null-terminated C string, so strlen reads past the heap buffer when no terminator is present. A local user or application must parse the file; the published proof of concept demonstrates an AddressSanitizer abort, not code execution.
Summary
What happened
Heap-buffer overflow in LIEF commit 5d1d643 allows attackers to crash the parser by supplying a crafted ELF core file. CorePrPsInfo::parse_ treats the fixed-width pr_fname field as a null-terminated C string, so strlen reads past the heap buffer when no terminator is present. A local user or application must parse the file; the published proof of concept demonstrates an AddressSanitizer abort, not code execution.
The record
- CVE
- CVE-2022-38306
- Published
- Sep 13, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- 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.
Public exploit references
- Issue 763 proof-of-concept ELF 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