Interpreter crash via missing data-section validation
Published Oct 23, 2023 · Updated Sep 17, 2024
Out-of-bounds write in wasm-interp in WebAssembly WABT 1.0.33 allows local users to crash the tool via a crafted WebAssembly module. DataSegment::Drop() writes through an absent data-segment entry when a malformed module declares a nonzero data count but omits the data section. Execution requires a user to open the crafted module with wasm-interp; the demonstrated consequence is a segmentation fault, not code execution.
Summary
What happened
Out-of-bounds write in wasm-interp in WebAssembly WABT 1.0.33 allows local users to crash the tool via a crafted WebAssembly module. DataSegment::Drop() writes through an absent data-segment entry when a malformed module declares a nonzero data count but omits the data section. Execution requires a user to open the crafted module with wasm-interp; the demonstrated consequence is a segmentation fault, not code execution.
The record
- CVE
- CVE-2023-46332
- Published
- Oct 23, 2023
- Updated
- Sep 17, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 23, 2023CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- Upstream crafted WebAssembly 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