CVE-2024-4671 is a high-severity use-after-free vulnerability in the Visuals component of Google Chrome. Improper object lifetime handling can leave freed memory accessible. An attacker that has already compromised a Chrome renderer process can trigger the condition with crafted HTML content and potentially cross the renderer security boundary to escape Chrome's sandbox. Google Chrome versions before 124.0.6367.201 are affected.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Chromium-family browser vulnerability included in the Gentoo advisory; no per-CVE technical details are provided.
A prior use-after-free vulnerability in Chrome's Visuals/Viz layer, referenced as historical context for recurring Viz compositor memory-safety issues.
A vulnerability in Google Chrome for Android (CVE-2024-4671) used as part of an exploit chain to deploy an infostealer payload targeting cookies, autofill data, and browsing history.
A high-severity Chrome use-after-free vulnerability in the Visuals component that may lead to code execution or application crash.
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.