CLI crash via unchecked func_ dereference
Published Apr 2, 2025 · Updated Apr 3, 2025
Null pointer dereference in WebAssembly WABT 1.0.36 allows remote attackers to crash wasm-interp with a crafted WebAssembly binary. The BeginFunctionBody method assigns func_ from an attacker-controlled function index without validating it, then writes code_offset through the resulting null pointer. Processing requires user interaction, and the invalid write terminates the affected command-line process.
Summary
What happened
Null pointer dereference in WebAssembly WABT 1.0.36 allows remote attackers to crash wasm-interp with a crafted WebAssembly binary. The BeginFunctionBody method assigns func_ from an attacker-controlled function index without validating it, then writes code_offset through the resulting null pointer. Processing requires user interaction, and the invalid write terminates the affected command-line process.
The record
- CVE
- CVE-2025-3122
- Published
- Apr 2, 2025
- Updated
- Apr 3, 2025
- Vendor
- WebAssembly
- Product
- WABT
- Classifications
- CWE-404, CWE-476, T1499.004, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 2, 2025CVE publishedPublication date reported by the CVE source.
- Apr 3, 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.36
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
- BeginFunctionBody-npd 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