Loading vulnerability…
A vulnerability in Mozilla Firefox, Firefox ESR, Firefox for Android, and Thunderbird allows an attacker to corrupt the methods of a JavaScript Array object via prototype pollution. This can result in the execution of attacker-controlled JavaScript code in a privileged context, potentially bypassing security boundaries within the browser or mail client.
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 browser exploit targeting Mozilla Firefox 100.0.1 on Windows, specifically exploiting CVE-2022-1802, CVE-2022-1529, and CVE-2022-2200. The exploit is implemented in JavaScript and HTML, with the main logic in 'exploit.html' and 'exploit.js'. The attack leverages prototype pollution via crafted IPC messages (Notification:Save) to manipulate the browser's internal object prototypes, followed by memory corruption techniques to gain arbitrary read/write primitives. The exploit chain culminates in privilege escalation or arbitrary code execution within the browser process. The repository includes a README with a reference to the tested Firefox version, and two minimal .mjs files unrelated to the exploit. The attack vector is browser-based, requiring the victim to open a malicious HTML file. The exploit demonstrates a high level of technical detail and operational maturity, but does not appear to be weaponized for mass exploitation.
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.
1 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.