Utility crash via corrupt ELF version metadata
Published Jan 27, 2023 · Updated Mar 28, 2025
NULL pointer dereference in GNU Binutils 2.39-7 allows local users to crash a utility by supplying a crafted ELF file. The _bfd_elf_get_symbol_version_string routine follows corrupt symbol-version metadata to a NULL pointer, causing illegal memory access. A user or automated workflow must process the file, and the resulting crash interrupts only the affected utility invocation.
Summary
What happened
NULL pointer dereference in GNU Binutils 2.39-7 allows local users to crash a utility by supplying a crafted ELF file. The _bfd_elf_get_symbol_version_string routine follows corrupt symbol-version metadata to a NULL pointer, causing illegal memory access. A user or automated workflow must process the file, and the resulting crash interrupts only the affected utility invocation.
The record
- CVE
- CVE-2022-4285
- Published
- Jan 27, 2023
- Updated
- Mar 28, 2025
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-476, T1204.002, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2023CVE publishedPublication date reported by the CVE source.
- Mar 28, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=binutils 2.39-7
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.
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