Process crash via invalid tekhex section traversal
Published Dec 5, 2024 · Updated Mar 14, 2025
Buffer overflow in GNU Binutils objdump 2.43 allows local users to crash the process by supplying a crafted tekhex file for inspection. BFD's tekhex first_phase function passes bfd_abs_section_ptr to bfd_get_next_section_by_name, causing an eight-byte read before _bfd_std_section. The file must be processed by objdump; the demonstrated consequence is an out-of-bounds read and process crash, while code execution remains unverified.
Summary
What happened
Buffer overflow in GNU Binutils objdump 2.43 allows local users to crash the process by supplying a crafted tekhex file for inspection. BFD's tekhex first_phase function passes bfd_abs_section_ptr to bfd_get_next_section_by_name, causing an eight-byte read before _bfd_std_section. The file must be processed by objdump; the demonstrated consequence is an out-of-bounds read and process crash, while code execution remains unverified.
The record
- CVE
- CVE-2024-53589
- Published
- Dec 5, 2024
- Updated
- Mar 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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