Service interruption via unreleased dynamic symbol storage
Published Aug 22, 2023 · Updated Oct 4, 2024
Memory exhaustion in GNU nm before 2.34 allows attackers to interrupt local service via crafted binary input processing. The display_rel_file path in binutils/nm.c retains its dyn_syms allocation instead of freeing it after use, so repeated processing continually consumes memory. Execution requires a user or workflow to invoke nm on attacker-influenced binary data; the bounded consequence is resource exhaustion and process or host-service interruption.
Summary
What happened
Memory exhaustion in GNU nm before 2.34 allows attackers to interrupt local service via crafted binary input processing. The display_rel_file path in binutils/nm.c retains its dyn_syms allocation instead of freeing it after use, so repeated processing continually consumes memory. Execution requires a user or workflow to invoke nm on attacker-influenced binary data; the bounded consequence is resource exhaustion and process or host-service interruption.
The record
- CVE
- CVE-2020-19724
- Published
- Aug 22, 2023
- Updated
- Oct 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 4, 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.
Weakness, pattern, technique
Public exploit references
- Sourceware Bug 25362 reproducerproof 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