A memory corruption vulnerability exists in Microsoft Internet Explorer 6 SP2 (versions 6.0.2900.2180 and 6.0.2800.1106, and earlier) due to improper handling of Javascript BODY onload events that call the window function. This can result in mismatched Document Object Model (DOM) objects, leading to memory corruption.
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 single Metasploit module: 'ms05_054_onload.rb', which exploits a remote code execution vulnerability (CVE-2005-1790) in Microsoft Internet Explorer 6 on Windows XP and Windows 2000. The exploit leverages a flaw in the JavaScript 'onLoad' handler and the 'window()' function, using a heap spray technique via JavaScript to place shellcode in memory. The module sets up an HTTP server that serves a malicious HTML/JavaScript page to the victim. When the victim visits the page with a vulnerable browser, the exploit triggers, resulting in arbitrary code execution. The payload is fully customizable using Metasploit's payload system, allowing for reverse shells, Meterpreter sessions, or other post-exploitation actions. The exploit requires that popups are allowed in the browser. The repository is structured as a standard Metasploit module, written in Ruby, with embedded JavaScript for the client-side exploit. No hardcoded IPs, domains, or file paths are present; the main fingerprintable endpoint is the attacker's HTTP server delivering the exploit.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.