Interpreter crash via out-of-bounds heap write
Published Nov 8, 2024 · Updated Nov 18, 2024
Heap buffer overflow in Kanaka WAC commit 385e1 allows local users to crash the interpreter with a crafted WebAssembly file. In interpret at wa.c:993, module loading performs a one-byte write immediately before a one-byte heap allocation, as demonstrated by AddressSanitizer. Exploitation requires local execution of the crafted file through wace and interrupts only that interpreter process; no confidentiality or integrity impact is reported.
Summary
What happened
Heap buffer overflow in Kanaka WAC commit 385e1 allows local users to crash the interpreter with a crafted WebAssembly file. In interpret at wa.c:993, module loading performs a one-byte write immediately before a one-byte heap allocation, as demonstrated by AddressSanitizer. Exploitation requires local execution of the crafted file through wace and interrupts only that interpreter process; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2024-35410
- Published
- Nov 8, 2024
- Updated
- Nov 18, 2024
- Vendor
- Kanaka
- Product
- WAC
- Classifications
- CWE-120, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2024CVE publishedPublication date reported by the CVE source.
- Nov 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=385e1
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
- Crafted WebAssembly 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