Crash via undersized DWARF address bounds check
Published Apr 3, 2023 · Updated Feb 13, 2025
Heap buffer over-read in GNU Binutils 2.39 allows local users to crash BFD-based tools by supplying a crafted DWARF file. In read_indexed_address, the bounds check reserves unit->offset_size bytes even when bfd_getl64 reads unit->addr_size bytes from .debug_addr. A user or automated workflow must make a BFD-consuming utility parse the malformed file; public evidence establishes an illegal memory access and crash, not code execution.
Summary
What happened
Heap buffer over-read in GNU Binutils 2.39 allows local users to crash BFD-based tools by supplying a crafted DWARF file. In read_indexed_address, the bounds check reserves unit->offset_size bytes even when bfd_getl64 reads unit->addr_size bytes from .debug_addr. A user or automated workflow must make a BFD-consuming utility parse the malformed file; public evidence establishes an illegal memory access and crash, not code execution.
The record
- CVE
- CVE-2023-1579
- Published
- Apr 3, 2023
- Updated
- Feb 13, 2025
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-119, CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=unknown
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