Local denial of service via unbounded data count
Published Jun 19, 2025 · Updated Jun 23, 2025
Resource exhaustion in WebAssembly WABT 1.0.0 through 1.0.37 allows local users to abort an interpreting process via a crafted Wasm file. BinaryReaderInterp::OnDataCount passes the file-supplied count directly to module_.datas.reserve without first imposing a practical allocation bound. Exploitation requires a local user to make wasm-interp or an integrating application parse the file; the bounded consequence is memory exhaustion and process termination.
Summary
What happened
Resource exhaustion in WebAssembly WABT 1.0.0 through 1.0.37 allows local users to abort an interpreting process via a crafted Wasm file. BinaryReaderInterp::OnDataCount passes the file-supplied count directly to module_.datas.reserve without first imposing a practical allocation bound. Exploitation requires a local user to make wasm-interp or an integrating application parse the file; the bounded consequence is memory exhaustion and process termination.
The record
- CVE
- CVE-2025-6274
- Published
- Jun 19, 2025
- Updated
- Jun 23, 2025
- Vendor
- WebAssembly
- Product
- WABT
- Classifications
- CWE-400, CWE-404, T1499.004
- 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?
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_4.txt reproducerproof 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