Module memory corruption via oversized invocation arguments
Published Oct 18, 2021 · Updated Aug 4, 2024
Buffer overflow in Go before 1.16.9 and 1.17.0 through 1.17.1 allows attackers to overwrite WebAssembly module memory via large function arguments. The wasm_exec.js runtime writes command-line arguments after the zero page without a size limit, allowing data beyond 4096 bytes to overwrite the module data section. Exposure requires a module built with GOARCH=wasm and GOOS=js and an invocation path that supplies attacker-controlled arguments; the reported consequence is corruption of module memory.
Summary
What happened
Buffer overflow in Go before 1.16.9 and 1.17.0 through 1.17.1 allows attackers to overwrite WebAssembly module memory via large function arguments. The wasm_exec.js runtime writes command-line arguments after the zero page without a size limit, allowing data beyond 4096 bytes to overwrite the module data section. Exposure requires a module built with GOARCH=wasm and GOOS=js and an invocation path that supplies attacker-controlled arguments; the reported consequence is corruption of module memory.
The record
- CVE
- CVE-2021-38297
- Published
- Oct 18, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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
No public exploit references are available in this record.
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