Memory corruption via unrestricted instruction width
Published Jan 29, 2025 · Updated Feb 12, 2025
Stack-based buffer overflow in GNU Binutils objdump 2.43 and earlier allows remote attackers to corrupt memory via a crafted object file. disassemble_bytes formats instruction bytes into a fixed 50-byte stack buffer while caller-controlled insn_width can exceed its capacity. Exploitation requires a user to run objdump disassembly with an oversized instruction width on the crafted file, causing memory corruption or a crash.
Summary
What happened
Stack-based buffer overflow in GNU Binutils objdump 2.43 and earlier allows remote attackers to corrupt memory via a crafted object file. disassemble_bytes formats instruction bytes into a fixed 50-byte stack buffer while caller-controlled insn_width can exceed its capacity. Exploitation requires a user to run objdump disassembly with an oversized instruction width on the crafted file, causing memory corruption or a crash.
The record
- CVE
- CVE-2025-0840
- Published
- Jan 29, 2025
- Updated
- Feb 12, 2025
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-121, CWE-119, CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 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=2.0
- Affected versionversion=2.1
- Affected versionversion=2.10
- Affected versionversion=2.11
- Affected versionversion=2.12
- Affected versionversion=2.13
- Affected versionversion=2.14
- Affected versionversion=2.15
- Affected versionversion=2.16
- Affected versionversion=2.17
- Affected versionversion=2.18
- Affected versionversion=2.19
- Affected versionversion=2.2
- Affected versionversion=2.20
- Affected versionversion=2.21
- Affected versionversion=2.22
- Affected versionversion=2.23
- Affected versionversion=2.24
- Affected versionversion=2.25
- Affected versionversion=2.26
- Affected versionversion=2.27
- Affected versionversion=2.28
- Affected versionversion=2.29
- Affected versionversion=2.3
- Affected versionversion=2.30
- Affected versionversion=2.31
- Affected versionversion=2.32
- Affected versionversion=2.33
- Affected versionversion=2.34
- Affected versionversion=2.35
- Affected versionversion=2.36
- Affected versionversion=2.37
- Affected versionversion=2.38
- Affected versionversion=2.39
- Affected versionversion=2.4
- Affected versionversion=2.40
- Affected versionversion=2.41
- Affected versionversion=2.42
- Affected versionversion=2.43
- Affected versionversion=2.5
- Affected versionversion=2.6
- Affected versionversion=2.7
- Affected versionversion=2.8
- Affected versionversion=2.9
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
- objdump crafted-file proof of conceptproof 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