Loading vulnerability…
CVE-2021-38297 is an out-of-bounds write vulnerability in Go WebAssembly programs compiled with GOARCH=wasm and GOOS=js. Before Go 1.16.9, and in the Go 1.17 branch before 1.17.2, invoking a function from a WASM module with excessively large command-line arguments can overflow the argument buffer and overwrite global data.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a comprehensive proof-of-concept (POC) for exploiting CVE-2021-38297, a buffer overflow vulnerability in Go's WebAssembly (WASM) loader (wasm_exec.js) prior to version 1.17.2. The repository contains a vulnerable web application ('vuln-twitter') built with Node.js and a Go-compiled WASM module used for processing post and comment content. The exploit leverages the lack of bounds checking on the 'argv' argument passed to the WASM module, allowing an attacker to submit an oversized comment that overflows the WASM linear memory and overwrites the content of another user's post at a hardcoded memory address (0x5000). This results in a stored XSS-like effect, where the altered post (potentially containing a malicious link) is displayed to all users. The repository includes all necessary code for the server, client, WASM module, and exploit payloads, as well as detailed documentation and reproduction steps. The exploit is a POC and does not include weaponized payloads, but demonstrates a real-world impact and provides a patching method by upgrading Go to a non-vulnerable version.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.