Crash and heap-data disclosure via uninitialized allocation
Published Jan 4, 2021 · Updated Aug 4, 2024
Use of uninitialized memory in GNU Binutils before 2.34 allows attackers to crash the processing tool or read heap data via a crafted file. In tic4x_print_cond, xmalloc reserves 32 bytes but initializes only 20 before fprintf_func can consume the remaining heap bytes. Exploitation requires the crafted file to be processed through the affected TMS320C3x/C4x disassembler path; the bounded consequences are a process crash or disclosure of residual heap data.
Summary
What happened
Use of uninitialized memory in GNU Binutils before 2.34 allows attackers to crash the processing tool or read heap data via a crafted file. In tic4x_print_cond, xmalloc reserves 32 bytes but initializes only 20 before fprintf_func can consume the remaining heap bytes. Exploitation requires the crafted file to be processed through the affected TMS320C3x/C4x disassembler path; the bounded consequences are a process crash or disclosure of residual heap data.
The record
- CVE
- CVE-2020-35494
- Published
- Jan 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-908, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 4, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=binutils 2.34
What conditions does exploitation require?
What is affected?
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.
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