Objdump crash via uninitialized symbol owner
Published Aug 22, 2023 · Updated Oct 3, 2024
Uninitialized-symbol handling in GNU Binutils objdump before 2.39.3 allows local users to crash the utility with a crafted Mach-O file. bfd_mach_o_get_synthetic_symtab leaves the asymbol the_bfd owner field uninitialized, and compare_symbols later dereferences it while sorting synthetic symbols. The flaw requires objdump to inspect attacker-supplied input; upstream GNU Binutils and Red Hat dispute treating inspection-tool crashes as security vulnerabilities.
Summary
What happened
Uninitialized-symbol handling in GNU Binutils objdump before 2.39.3 allows local users to crash the utility with a crafted Mach-O file. bfd_mach_o_get_synthetic_symtab leaves the asymbol the_bfd owner field uninitialized, and compare_symbols later dereferences it while sorting synthetic symbols. The flaw requires objdump to inspect attacker-supplied input; upstream GNU Binutils and Red Hat dispute treating inspection-tool crashes as security vulnerabilities.
The record
- CVE
- CVE-2022-47695
- Published
- Aug 22, 2023
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 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.
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
- Sourceware Bug 29846 proof of conceptproof of concept · unverified
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