Local crash via LogOpcode reachable assertion
Published Jun 19, 2025 · Updated Jun 23, 2025
Reachable assertion in WABT 1.0.0 through 1.0.37 allows local users to crash wasm-objdump with a crafted WebAssembly binary. An invalid element-section initializer invokes OnCallIndirectExpr outside a function body, and LogOpcode asserts that the disassembler is inside one. Exploitation requires local control of an input processed for disassembly; the abort affects that process, and the upstream maintainer disputes real-world reachability.
Summary
What happened
Reachable assertion in WABT 1.0.0 through 1.0.37 allows local users to crash wasm-objdump with a crafted WebAssembly binary. An invalid element-section initializer invokes OnCallIndirectExpr outside a function body, and LogOpcode asserts that the disassembler is inside one. Exploitation requires local control of an input processed for disassembly; the abort affects that process, and the upstream maintainer disputes real-world reachability.
The record
- CVE
- CVE-2025-6273
- Published
- Jun 19, 2025
- Updated
- Jun 23, 2025
- Vendor
- WebAssembly
- Product
- WABT
- Classifications
- CWE-617
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2025CVE publishedPublication date reported by the CVE source.
- Jun 23, 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=1.0.0
- Affected versionversion=1.0.1
- Affected versionversion=1.0.10
- Affected versionversion=1.0.11
- Affected versionversion=1.0.12
- Affected versionversion=1.0.13
- Affected versionversion=1.0.14
- Affected versionversion=1.0.15
- Affected versionversion=1.0.16
- Affected versionversion=1.0.17
- Affected versionversion=1.0.18
- Affected versionversion=1.0.19
- Affected versionversion=1.0.2
- Affected versionversion=1.0.20
- Affected versionversion=1.0.21
- Affected versionversion=1.0.22
- Affected versionversion=1.0.23
- Affected versionversion=1.0.24
- Affected versionversion=1.0.25
- Affected versionversion=1.0.26
- Affected versionversion=1.0.27
- Affected versionversion=1.0.28
- Affected versionversion=1.0.29
- Affected versionversion=1.0.3
- Affected versionversion=1.0.30
- Affected versionversion=1.0.31
- Affected versionversion=1.0.32
- Affected versionversion=1.0.33
- Affected versionversion=1.0.34
- Affected versionversion=1.0.35
- Affected versionversion=1.0.36
- Affected versionversion=1.0.37
- Affected versionversion=1.0.4
- Affected versionversion=1.0.5
- Affected versionversion=1.0.6
- Affected versionversion=1.0.7
- Affected versionversion=1.0.8
- Affected versionversion=1.0.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
- wabt_crash.txt proof-of-concept inputproof 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