Mozilla Firefox 1.5, Thunderbird 1.5 when JavaScript is enabled for mail, and SeaMonkey versions before 1.0 contain a memory-corruption flaw in the QueryInterface method of the built-in Location and Navigator objects. Processing attacker-controlled web or email content can trigger the corruption and may permit arbitrary code execution.
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 (2 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/browser/firefox_queryinterface.rb) that exploits a code execution vulnerability (CVE-2006-0295) in Mozilla Firefox 1.5.0.0 on Mac OS X and Linux. The module acts as an HTTP server, delivering a specially crafted HTML page with embedded JavaScript to the victim. When a user visits the malicious page, the JavaScript performs a heap spray to fill memory with a NOP sled and the encoded payload, then triggers the vulnerability via the location.QueryInterface() call. If successful, this results in arbitrary code execution in the context of the browser. The exploit is operational and allows the attacker to select and deliver a custom Metasploit payload. The code is written in Ruby (Metasploit module), with embedded JavaScript and HTML for the client-side exploit. The main attack vector is browser-based, requiring user interaction (visiting the attacker's page).
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.