Objdump crash via unchecked allocation result
Published Jan 4, 2021 · Updated Aug 4, 2024
NULL pointer dereference in GNU Binutils before 2.34 allows local users to crash objdump by opening a crafted PEF file. In bfd_pef_parse_symbols in bfd/pef.c, bfd_bread writes through the result of bfd_malloc without first checking whether allocation returned NULL. Exploitation requires a user to process attacker-supplied input with a build that includes PEF support, and the resulting impact is limited to an objdump process crash.
Summary
What happened
NULL pointer dereference in GNU Binutils before 2.34 allows local users to crash objdump by opening a crafted PEF file. In bfd_pef_parse_symbols in bfd/pef.c, bfd_bread writes through the result of bfd_malloc without first checking whether allocation returned NULL. Exploitation requires a user to process attacker-supplied input with a build that includes PEF support, and the resulting impact is limited to an objdump process crash.
The record
- CVE
- CVE-2020-35495
- Published
- Jan 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-476, 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?
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