Loading vulnerability…
CVE-2021-30632 is a high-severity memory corruption vulnerability in the V8 JavaScript engine used by Google Chrome. In affected Chrome versions prior to 93.0.4577.82, a remote attacker could trigger an out-of-bounds write by causing V8 to process crafted web content. Public reporting also characterizes the issue as a type-confusion condition in V8 that can lead to heap corruption and remote code execution. The flaw is reachable through a crafted HTML page that drives vulnerable JavaScript engine behavior.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2021-30632, a vulnerability in the V8 JavaScript engine used by Google Chrome. The exploit is implemented as a single HTML file (CVE-2021-30632.html) containing JavaScript code that leverages a vulnerability to achieve out-of-bounds access, arbitrary read/write primitives, and ultimately remote code execution (RCE) by injecting and executing shellcode. The shellcode provided launches 'calc.exe' as a demonstration of code execution. The exploit targets Chrome versions 91, 92, and 93.0.4577.63 on Windows. The README provides references and credits but does not contain code. The main entry point is the HTML file, which, when opened in a vulnerable version of Chrome, will execute the exploit. No network endpoints or external domains are referenced; the exploit is fully self-contained and operates in the context of the browser.
This repository is a proof-of-concept (PoC) exploit for CVE-2021-30632, an out-of-bounds write vulnerability in the V8 JavaScript engine, as used in browsers such as Samsung Internet Browser v15.0.2.47. The repository contains two files: a README.md describing the vulnerability and exploitation approach, and poc.html, which implements the exploit. The HTML file contains JavaScript code that manipulates array types and leverages JIT optimizations to achieve type confusion, resulting in out-of-bounds read/write primitives. The exploit then uses these primitives to gain arbitrary memory access, constructs a WebAssembly instance to obtain an RWX memory region, writes a small aarch64 shellcode (RET 0xDEAD) into it, and executes it. The result is displayed in the browser. There are no hardcoded network endpoints or external resources; the exploit is self-contained and must be loaded in a vulnerable browser to demonstrate the issue. The code is a PoC and does not include weaponized features such as remote command execution or persistence.
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.
A previously disclosed V8 vulnerability cited as another example of recurring weaknesses in V8 Map-tracking logic.
A Chrome remote code execution vulnerability described as a type confusion bug, used with CVE-2021-30633 in an in-the-wild exploit chain.
A high-severity out-of-bounds write vulnerability in Chrome's V8 JavaScript engine.
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.