Local crash via read-only symbol-name write
Published Jan 21, 2025 · Updated Mar 18, 2025
Improper access control in GNU Binutils nm 2.43 and later allows local users to crash nm via a crafted ELF symbol table. When --without-symbol-versions is used, print_symname replaces an @ byte inside a memory-mapped, read-only symbol name with NUL instead of copying it. Exploitation requires a user to run nm with that option on a corrupt ELF file; the resulting invalid write terminates only the nm process.
Summary
What happened
Improper access control in GNU Binutils nm 2.43 and later allows local users to crash nm via a crafted ELF symbol table. When --without-symbol-versions is used, print_symname replaces an @ byte inside a memory-mapped, read-only symbol name with NUL instead of copying it. Exploitation requires a user to run nm with that option on a corrupt ELF file; the resulting invalid write terminates only the nm process.
The record
- CVE
- CVE-2024-57360
- Published
- Jan 21, 2025
- Updated
- Mar 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 18, 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.
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
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