CVE-2024-12381 is a high-severity type-confusion vulnerability in the V8 JavaScript and WebAssembly engine used by Google Chrome. Chrome versions prior to 131.0.6778.139 can incorrectly handle object types while processing attacker-controlled web content, enabling heap corruption through a crafted HTML page.
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 (1 hidden).
This repository contains a single Python Flask application, server.py, that acts as a covert browser fingerprinting and exploit-delivery server rather than a standalone exploit implementation. The server exposes a landing page (/, /index.html) that loads a disguised analytics script from /static/analytics.js. That embedded JavaScript collects client-side fingerprint data including a random session-like identifier, screen resolution, timezone, full user agent, and a parsed Chrome version string. It then POSTs the data to /api/v1/track, where the server logs the fingerprint and, if the client is marked vulnerable, responds with a redirect target /exploit. The vulnerability check in the provided script is simplistic and effectively treats any parsed major version >= 1 as vulnerable, so it functions more as a traffic-gating mechanism than a precise version matcher. The Flask app also supports serving local exploit artifacts via exploit.html and exploit.js, but those files are not included in this repository snapshot. Operationally, this is an exploit staging component for browser/web attacks: it fingerprints visitors, records telemetry in access.log, and conditionally delivers follow-on exploit content. The code references CVE-2024-12381 and a V8 sandbox bypass in comments, but the actual exploitation logic is absent from the repository; only the delivery infrastructure is present.
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.
4 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.