Mozilla Firefox 1.5 before 1.5.0.5 and SeaMonkey before 1.0.3 contain a vulnerability in the handling of the window navigator object during Java startup. A remote attacker can modify certain properties of window.navigator that are later accessed when Java initializes, triggering a crash condition that can be leveraged to achieve arbitrary code execution. The issue is exposed through malicious web content processed by a vulnerable browser with Java startup occurring in the affected context.
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: 'mozilla_navigatorjava.rb', which exploits CVE-2006-3677, a code execution vulnerability in Mozilla Firefox 1.5.0.4, Mozilla Suite, and Thunderbird when the Java plugin is enabled. The exploit works by serving a malicious HTML/JavaScript page to the victim's browser. If the browser has Java enabled, the script attempts to trigger the vulnerability and execute arbitrary code (Metasploit payload) on the target system. The module supports multiple platforms (Windows, Linux, Mac OS X) and architectures (x86, PPC). The exploit is operational and allows the attacker to run arbitrary code with the privileges of the user running the browser. The only fingerprintable endpoints are the HTTP server used to deliver the exploit and a reference URL to the Mozilla security advisory. The repository is structured as a typical Metasploit exploit module, with the main logic in the 'on_request_uri' and 'generate_html' methods.
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.
2 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.