Process crash via oversized ELF allocation
Published Jan 21, 2022 · Updated Aug 4, 2024
Resource exhaustion in bingrep 0.8.5 allows attackers to crash the process by supplying a crafted ELF file for analysis. ELF section-header parsing accepts inconsistent size metadata and requests an impossible 18,446,744,073,709,551,610-byte allocation, causing the allocator to abort. Exploitation requires the command-line tool to analyze the malformed file; the demonstrated consequence is termination of that bingrep process.
Summary
What happened
Resource exhaustion in bingrep 0.8.5 allows attackers to crash the process by supplying a crafted ELF file for analysis. ELF section-header parsing accepts inconsistent size metadata and requests an impossible 18,446,744,073,709,551,610-byte allocation, causing the allocator to abort. Exploitation requires the command-line tool to analyze the malformed file; the demonstrated consequence is termination of that bingrep process.
The record
- CVE
- CVE-2021-39480
- Published
- Jan 21, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2022CVE publishedPublication date reported by the CVE source.
- Aug 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
- Crafted ELF proof-of-concept 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