Loading vulnerability…
A use-after-free vulnerability exists in the GPU component of Google Chrome prior to version 92.0.4515.107. The flaw allows a remote attacker to trigger heap corruption by enticing a user to visit a specially crafted HTML page, leading to use of memory after it has been freed.
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 contains a proof-of-concept (PoC) exploit for CVE-2021-30573, a use-after-free vulnerability in Google Chrome versions 91.0.4472.77 and lower. The exploit consists of a single HTML file (poc-exploit.html) that, when opened in a vulnerable version of Chrome, triggers the vulnerability by leveraging a <select> element with an extremely large <option> value. The README.md provides context, usage instructions, and references to the CVE and official Chrome blog post. There are no network endpoints or external resources involved; the exploit is self-contained and demonstrates the vulnerability locally in the browser. The repository is structured simply, with the main exploit in the HTML file and documentation in the README.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.